Borrowing it
Nothing to install: this file belongs to BenchBox-dev/BenchBox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BenchBox-dev/BenchBox/develop/.claude/skills/tidy-perms/SKILL.mdgit clone --depth 1 https://github.com/BenchBox-dev/BenchBoxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/benchbox-dev/benchbox/tidy-perms)<a href="https://agentmods.dev/skills/benchbox-dev/benchbox/tidy-perms"><img src="https://agentmods.dev/badge/skills/benchbox-dev/benchbox/tidy-perms.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.00293 |
| Opus 5 | $0.00021 | $0.00147 |
| Sonnet 5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade B, and why
tidy-perms scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Never commit `settings.local.json`, `~/.codex/config.toml`, or What it actually says
Permissions Consolidation
Route below and read the selected action file. Keep unclear entries PERSONAL and ask for direction. Do not add, broaden, or relocate an entry when the change would permit, in the destination scope, a command that is not already allowed in that scope.
Actions
| Action | Trigger | Read |
|---|---|---|
consolidate |
default/tidy permissions | references/consolidate.md |
audit |
audit/review permissions | references/audit.md |
help |
help/list actions | this table |
Rules
- Never
git add -A; stage explicit project config paths only. - Never commit
settings.local.json,~/.codex/config.toml, or~/.gemini/*.json. - Preserve unrelated hooks and keys. Do not allowlist force-push, reset, clean, or removal commands. Remove a stale or conflicting executable hook only when its owner, conflict, and safe replacement are evidenced and the task authorizes personal configuration changes.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 32 lines · 42 tokens per session scan B 6966708341be
tidy-perms is a skill published in the GitHub repository BenchBox-dev/BenchBox (12 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 293 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…