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 agents/spica-engine/spica/product-managergit clone --depth 1 https://github.com/spica-engine/spicaWrote 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/agents/spica-engine/spica/product-manager)<a href="https://agentmods.dev/agents/spica-engine/spica/product-manager"><img src="https://agentmods.dev/badge/agents/spica-engine/spica/product-manager.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.00037 | $0.00972 |
| Opus 5 | $0.00018 | $0.00486 |
| Sonnet 5 | $0.00007 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
product-manager 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 3d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago First seen · 129 lines · 37 tokens per session scan A bacb27dabb8e
product-manager is an agent published in the GitHub repository spica-engine/spica (100 stars, last pushed 10d ago), licensed AGPL-3.0. It adds 37 tokens to every session and 972 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-09-01.
Other agents, from other repositories
docs-reviewer
Use this agent during PR review to answer two docs questions about any PR. Coverage, on every diff - does the change alter user-facing behavior that astro-docs documents in prose, without updating those docs? Compliance, when the diff touches docs content (astro-docs/src/content/ or astro-docs/sidebar.mts) - do the…
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
comment-analyzer
Use this agent during PR review to check that a PR's comments and doc-comments are TRUE. It verifies every load-bearing claim in a changed comment against the code it describes, and flags comments the diff left stale. It does not ask for more comments - this repo's committed CLAUDE.md rules default to no comment, so…
security-analyzer
Use this agent during PR review to hunt injection-class vulnerabilities in a PR's changes - command injection, zip-slip and path traversal, prototype pollution, SSRF, credential leakage, and unsafe deserialization. It reports a finding only when untrusted data actually crosses a trust boundary into a dangerous sink…
performance-analyzer
Use this agent during PR review to analyze the runtime performance of a PR's changes along two axes - (1) resource footprint (unnecessary CPU or memory usage) and (2) execution efficiency (does the code run quickly, avoid redundant work, and scale with workspace size). It reports a finding only when the cost is real…
alternative-approach
Use this agent during PR review to independently design alternative solutions to the problem a PR solves and contrast them with the PR's chosen approach. It reports a finding only when an alternative is materially better (root-cause vs symptom fix, reuse of an existing utility, large complexity reduction) or when the…