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/deepakkamboj/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/agents/deepakkamboj/claude-marketplace/reviewer)<a href="https://agentmods.dev/agents/deepakkamboj/claude-marketplace/reviewer"><img src="https://agentmods.dev/badge/agents/deepakkamboj/claude-marketplace/reviewer/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/deepakkamboj/claude-marketplace/reviewer"><img src="https://agentmods.dev/badge/agents/deepakkamboj/claude-marketplace/reviewer.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.00040 | $0.03376 |
| Opus 5 | $0.00020 | $0.01688 |
| Sonnet 5 | $0.00008 | $0.00675 |
| Haiku 4.5 | $0.00004 | $0.00338 |
Grade A, and why
reviewer 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 12d 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.
- 12d ago First seen · 402 lines · 40 tokens per session scan A 71ba9070a531
reviewer is an agent published in the GitHub repository deepakkamboj/claude-marketplace (5 stars, last pushed 7mo ago), with no licence file. It adds 40 tokens to every session and 3,376 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-08-31.
Other agents, from other repositories
cross-cli-consistency-checker
Audit all cli-web- CLIs for convention drift against skills/shared/CONVENTIONS.md, including replskin drift via cli-web-devkit drift and .manifest.json presence. Reports PASS/FAIL per check per CLI in a matrix format. Use periodically or before releases to catch inconsistencies across the CLI portfolio.
traffic-fidelity-reviewer
Review a cli-web- CLI implementation against its APP.md API map. Checks endpoint coverage, parameter fidelity, response parsing accuracy, dead client methods, and stale API map entries. Returns scored findings. Use during Phase 4 standards review — dispatched by the standards skill.
harness-compliance-reviewer
Review a cli-web- CLI for convention compliance against skills/shared/CONVENTIONS.md. Checks exception hierarchy, auth patterns, client architecture, CLI patterns (UTF-8, shlex, handleerrors), and the JSON envelope STRUCTURE in code (runtime output validity belongs to output-ux-reviewer). Returns scored findings. Use…
e2e-failure-classifier
Use when a Playwright or Cypress test failure needs a root cause, to classify ONE failure into the F1–F15 taxonomy shared by playwright-debugger and cypress-debugger. Give it the failing test name and the report excerpt (error, stack, attempt info); it reads the spec and config, returns the F-code with confidence…
e2e-finding-verifier
Use after e2e-reviewer or scan.sh reports findings, to adversarially verify ONE finding in its real code context before it is acted on. Give it the pattern ID, file:line, and the flagged snippet; it reads the surrounding spec, project config, and the pattern contract, tries to REFUTE the finding first, and returns…
wp-audit-practices
WordPress coding standards auditor — escaping, sanitization, enqueueing, theme supports, hooks, i18n, code quality.