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/mantacron/mantaWrote 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/mantacron/manta/product-manager)<a href="https://agentmods.dev/agents/mantacron/manta/product-manager"><img src="https://agentmods.dev/badge/agents/mantacron/manta/product-manager/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/agents/mantacron/manta/product-manager"><img src="https://agentmods.dev/badge/agents/mantacron/manta/product-manager.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.00039 | $0.00876 |
| Opus 5.5 | $0.00016 | $0.00350 |
| Sonnet 5.5 | $0.00008 | $0.00175 |
| Haiku 4.5 | $0.00004 | $0.00088 |
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 1mo 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago First seen · 114 lines · 39 tokens per session scan A 1fab096a6016
product-manager is an agent published in the GitHub repository mantacron/manta (10 stars, last pushed 22d ago), with no licence file. It adds 39 tokens to every session and 876 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
backlog-reader
Launched by /aidex:backlog detect-resolved; not for direct use. Reads a batch of backlog items (about five) and the paths and commits each cites, and returns one verdict per item (resolved / partially / not) with a cited path or commit. Read-only; never closes or edits an item.
backlog-filer
Use proactively when findings a run produced must be registered as backlog items ("file these as backlog items", "register these findings", out-of-scope bugs a delegate reported). Handoff: the findings (one line each, with reproduction or evidence), the target project root, the origin (and its --plan / --worklist /…
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
ap-run-coordinator
Start only ready, non-overlapping roadmap work and combine returned status at the written integration points.
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.