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/perf-analyzer)<a href="https://agentmods.dev/agents/mantacron/manta/perf-analyzer"><img src="https://agentmods.dev/badge/agents/mantacron/manta/perf-analyzer/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/perf-analyzer"><img src="https://agentmods.dev/badge/agents/mantacron/manta/perf-analyzer.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.00000 | $0.02743 |
| Opus 5.5 | $0.00000 | $0.01097 |
| Sonnet 5.5 | $0.00000 | $0.00549 |
| Haiku 4.5 | $0.00000 | $0.00274 |
Grade A, and why
perf-analyzer 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 Changed · +27 lines 9c852c341694
- 1mo ago First seen · 256 lines · 0 tokens per session scan A 846b2efecb49
perf-analyzer is an agent published in the GitHub repository mantacron/manta (10 stars, last pushed 15d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 2,743 tokens. 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
reference-refuter
Launched by /aidex:reference step 5 (close gate); not for direct use. Returns a verdict per claim of a reference module.
review-diff-opus
Use proactively on a delegate's returned diff, before the main session commits it, when the diff adds or moves a comparison, a quantifier, a boundary or a null/empty branch inside a predicate - whatever model wrote it and however green its gate. That is the shape of defect a passing gate hides. Reads the diff…
bug-hunter
Incident Responder & Debugger (Trigger with raw logs).
jd-fix-agent
You are a judgment-day surgical fix agent. Execute the fix instructions provided in the delegate prompt exactly.
evidence-based-investigator
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…
jd-fix-agent
Judgment Day surgical fix agent for confirmed findings. Can edit code and run focused tests.