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.
npx agentmods add commands/juanmhidalgo/claude-plugins/stagedgit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/staged)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/staged"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/staged.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 | $0.00035 | $0.00529 |
| Opus 5 | $0.00017 | $0.00264 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
staged scanned grade A with 0 findings 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 4d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Context
- Current branch: !
git branch --show-current - Staged files: !
git diff --cached --name-only
Staged Changes Summary
!git diff --cached --stat
Instructions
Use Agent tool with subagent_type="code-review:branch-reviewer" to perform a comprehensive code review of staged changes.
Review process:
- Get staged diff:
git diff --cached - For large diffs, review file by file:
git diff --cached -- <file> - Read full files when needed for context
Analysis focus:
- Security vulnerabilities (injection, auth issues, secrets)
- Performance problems (N+1 queries, memory leaks, blocking calls)
- Bug risks (edge cases, null checks, race conditions)
- Code quality (readability, maintainability, SOLID principles)
- Missing tests for new/changed functionality
Output format: Organize findings by severity:
- CRITICAL: Must fix before commit (security, data loss risks)
- HIGH: Should fix (bugs, performance issues)
- MEDIUM: Recommended (code quality, maintainability)
- LOW: Suggestions (style, minor improvements)
Include file path, line numbers, and concrete fix suggestions.
Important:
- Do NOT modify any code
- Do NOT stage or commit changes
- Focus on the diff, not entire files
Next Step
After completing the review, suggest:
"To create a trackable fixes document, run
/code-review/fixes-plan [feature-name]"
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.
- 4d ago First seen · 70 lines · 35 tokens per session scan A 1c00466f932e
staged is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 9d ago), licensed MIT. It adds 35 tokens to every session and 529 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
brooks-audit
Run a Brooks-Lint architecture audit.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
init
Install the formatters this repository needs, with every command visible before it runs.
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.