PermitLint
Are these coding-agent permissions broader, weaker, or less effective than they look?
agent-tools permissions . --jsonAgent Tools · Collection 01
Audit permissions, resolve instruction scope, review configuration changes, lint hooks, and prove packaged plugins without learning five installation flows.
npx --yes --registry=https://codeberg.org/api/packages/automa-tan/npm/ agent-tools@latest list
Pick the question
Friendly aliases route to exact published releases. Each specialist stays independently versioned and independently useful.
Are these coding-agent permissions broader, weaker, or less effective than they look?
agent-tools permissions . --jsonWhich AGENTS.md, CLAUDE.md, imports, and scoped rules actually apply here?
agent-tools rules --target . --harness auto --jsonWhat capability changed in this working tree, staged diff, or Git range?
agent-tools diff . --staged --jsonWill this hook configuration be accepted, skipped, duplicated, or misread?
agent-tools hooks --target . --harness auto --jsonDoes the package contain what its Codex and Claude Code manifests promise—without loading the plugin?
agent-tools plugins . --harness both --checkAgent Skill bundle
One router plus a focused workflow for every checker lets Codex and Claude Code select the narrowest useful check without loading unrelated guidance.
The dispatcher pins every specialist. Run agent-tools list --json to see precisely what will execute.
The checkers parse the configuration in scope. They do not turn static evidence into claims about a running harness.
Use the bundle for convenience or install any specialist alone. Nothing requires adopting the rest of the collection.