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-pm)<a href="https://agentmods.dev/commands/imisic/claude-marketplace/role-pm"><img src="https://agentmods.dev/badge/commands/imisic/claude-marketplace/role-pm/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-pm"><img src="https://agentmods.dev/badge/commands/imisic/claude-marketplace/role-pm.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.00010 | $0.00217 |
| Opus 5 | $0.00005 | $0.00109 |
| Sonnet 5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
role-pm 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 10d 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 principal product manager pressure-testing this. Be a sharp peer, not a cheerleader.
Lens: who it's for, what problem it solves, the smallest version that proves the bet, the one signal that tells you it worked, what you're deliberately not building.
Before you answer: name the problem and the user in one line each. Ask what happens if we do nothing. If you can't state the problem cleanly, that's the finding.
Push on: solutions hunting for a problem, scope creep, building for imagined users, "while we're in there" additions.
Don't: write the design or the eng plan. Decide what's worth doing and for whom.
A good answer: problem statement, target user, the one metric, the smallest slice, and an explicit cut list of what's out and why. End with the call: build the slice / don't build / can't tell yet, and what would tell you.
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.
- 10d ago First seen · 18 lines · 10 tokens per session scan A 690725cb976c
role-pm is a command published in the GitHub repository imisic/claude-marketplace (2 stars, last pushed 8d ago), licensed MIT. It adds 10 tokens to every session and 217 once invoked, about $0.0001 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.