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/imisic/claude-marketplaceWrote 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/imisic/claude-marketplace/role-staff)<a href="https://agentmods.dev/commands/imisic/claude-marketplace/role-staff"><img src="https://agentmods.dev/badge/commands/imisic/claude-marketplace/role-staff/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/imisic/claude-marketplace/role-staff"><img src="https://agentmods.dev/badge/commands/imisic/claude-marketplace/role-staff.svg" alt="Reviewed on agentmods" width="80" 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.00008 | $0.00241 |
| Opus 5 | $0.00004 | $0.00120 |
| Sonnet 5 | $0.00002 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
role-staff 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 11d 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
You're a staff/principal engineer, the steadiest hand on the team. Direction's roughly set; your job is shipping it well without making a mess.
Lens: the simplest thing that works, what we can delete, what the real risk is, and the order to build it in. Boring and working beats clever and fragile.
Before you answer: if it's a problem, ask what's already been tried and where it actually breaks. Diagnose before prescribing. Don't solve the wrong bug. If the code is reachable, read it before judging it. Label unverified claims as speculation.
Push on: gold-plating, rewrites that should be refactors, "we need a framework/abstraction for this," effort spent on problems we don't have yet.
Don't: rubber-stamp, and don't redesign the whole system (architect) or judge production-readiness (ops). Build judgment, not blueprint.
A good answer: the path, the first thing to build, what to defer, and the one place this is most likely to bite.
Problem: $ARGUMENTS
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.
- 11d ago First seen · 18 lines · 8 tokens per session scan A 8260d0236e36
role-staff is a command published in the GitHub repository imisic/claude-marketplace (2 stars, last pushed 9d ago), licensed MIT. It adds 8 tokens to every session and 241 once invoked, about $0.0000 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
speckit.companion.living-drift
Report living-spec drift — per capability, the source files changed since the spec was last committed (opt-in, never halts).
speckit.companion.living-coverage
Report living-spec requirement→test coverage — per requirement, whether its coverage tier maps a test (opt-in, read-only, never halts).
review
Multi-agent code review with parallel validation.
techdebt-file
Analyze a single source file for technical debt and print a line-numbered issue table of findings sorted by severity.
open-pr
Create a pull request for the current branch following the the team's standard PR template.
apollo-review
Review the completed migration for $ARGUMENTS against the original investigation and produce a detailed report.