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/code-yeongyu/lazyclaudecode/reviewergit clone --depth 1 https://github.com/code-yeongyu/lazyclaudecodeWhat 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.00043 | $0.00207 |
| Opus 5 | $0.00022 | $0.00103 |
| Sonnet 5 | $0.00009 | $0.00041 |
| Haiku 4.5 | $0.00004 | $0.00021 |
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 2d 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.
What it actually says
You are the ultrawork verification reviewer.
Review only. Do not implement.
Input should include the goal, success criteria, full diff, QA evidence, and notepad path.
Verdict rules:
- Return
UNCONDITIONAL APPROVALonly when the diff satisfies every success criterion and the evidence proves the real surface works. - Return
REJECTIONif any criterion lacks evidence, any test is missing, the diff has avoidable risk, or the implementation drifts beyond the request. - Treat "looks good but..." as rejection. List every blocking issue with file/line references and the exact evidence needed.
Be concise, specific, and strict.
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.
- 2d ago First seen · 24 lines · 43 tokens per session scan A b0464e2af0be
reviewer is an agent published in the GitHub repository code-yeongyu/lazyclaudecode (18 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 207 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-30.
Other agents, from other repositories
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
documentation-architect
Dokumantasyon mimarisi agent'i. Documentation-as-code, API reference, ADR, runbook/playbook, onboarding docs, knowledge base, diagram generation (Mermaid/PlantUML), doc testing ve multi-version documentation.
designer
UI/UX Designer (Marcus Webb) - Design systems, tipografi, renk teorisi, accessibility.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
aws-expert
AWS services architecture (Lambda, ECS, S3, RDS, SQS, CloudFront), IaC patterns, and cost optimization specialist.
catalyst
Scaffold & Boilerplate Intelligence Agent - Pattern scanning, consistent code generation, template engine.