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/MANOJ21K/agentic-code-reviewWrote 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/manoj21k/agentic-code-review/bug-hunter)<a href="https://agentmods.dev/agents/manoj21k/agentic-code-review/bug-hunter"><img src="https://agentmods.dev/badge/agents/manoj21k/agentic-code-review/bug-hunter/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/manoj21k/agentic-code-review/bug-hunter"><img src="https://agentmods.dev/badge/agents/manoj21k/agentic-code-review/bug-hunter.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.00078 | $0.00536 |
| Opus 5.5 | $0.00031 | $0.00214 |
| Sonnet 5.5 | $0.00016 | $0.00107 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
bug-hunter 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 46 lines · 78 tokens per session scan A 185e90302508
bug-hunter is an agent published in the GitHub repository MANOJ21K/agentic-code-review (2 stars, last pushed 3mo ago), with no licence file. It adds 78 tokens to every session and 536 once invoked, about $0.0003 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
minimal-fixer
A focused bug-fixing agent that changes the implementation to make an existing failing reproduction test pass. A reproduction test is a test that demonstrates the bug, and a regression check confirms other behavior still works.
tldrcrew-investigator
Read-only code locator. Returns file:line table for "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Output is tldr-compressed so the main thread eats fewer tokens. Refuses to suggest fixes.
Tenable Host Doctor
Diagnoses why a single host failed a Tenable credentialed scan, from its .nessus export.
prod-logs
Pulls recent production logs filtered for errors, warnings, and anomalies, a quick health check after any deploy, after a load test, or any time you want to know if something is going wrong. Treats logs as the only acceptable primary source for incident analysis.
greplm-search
Code search agent for exploring any codebase. Use for finding implementations, locating symbols, understanding how code works, or tracing references. Prefer over Bash/Read for exploratory codebase search.
greplm-search
Code search agent for exploring any codebase. Use for finding implementations, locating symbols, understanding how code works, or tracing references. Prefer over Bash/Read for exploratory codebase search.