Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/rohitg00/pro-workflowWrote 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/commands/rohitg00/pro-workflow/permission-tuner)<a href="https://agentmods.dev/commands/rohitg00/pro-workflow/permission-tuner"><img src="https://agentmods.dev/badge/commands/rohitg00/pro-workflow/permission-tuner.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.00015 | $0.00203 |
| Opus 5 | $0.00008 | $0.00102 |
| Sonnet 5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade C, and why
permission-tuner scanned grade C 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 8d ago.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Auto-deny**: Dangerous operations (rm -rf, git push --force) The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 8d ago First seen · 33 lines · 15 tokens per session scan C 1f1d9d6dafb3
permission-tuner is a command published in the GitHub repository rohitg00/pro-workflow (2,811 stars, last pushed 6d ago), with no licence file. It adds 15 tokens to every session and 203 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
commit
Quality-gated commit — runs lint/typecheck/test (if configured), reviews the staged diff, drafts a conventional-commits message, and commits.
context-size
Snapshot the current session's context footprint — transcript size, CLAUDE.md size, MCP schemas, file reads still in context. Identifies what's eating tokens so you can trim.
mcp-audit
Audit the MCP servers active in this session — tool count, schema size, and which ones probably aren't pulling their weight. Every MCP tool's schema adds tokens to every turn; disabling the unused ones is a direct cost cut.
permission-tune
Analyze your Claude Code permission setup — flag commands that probably deserve an allowlist entry, dangerous defaults that should be on the denylist, and suggest additions to settings.json. Reduces prompt fatigue without loosening safety.
adr
Draft an Architectural Decision Record (ADR) for a proposed or accepted decision. Uses the MADR-style template and places it in docs/adr/ or adrs/ (whichever the repo uses).
sec-scan
Security scan on the diff — SAST heuristics, secret regex sweep, dependency advisory check. Delegates to @security-reviewer.