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/NikiforovAll/lazyclaudeWrote 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/commands/nikiforovall/lazyclaude/run-quality-gates)<a href="https://agentmods.dev/commands/nikiforovall/lazyclaude/run-quality-gates"><img src="https://agentmods.dev/badge/commands/nikiforovall/lazyclaude/run-quality-gates/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/commands/nikiforovall/lazyclaude/run-quality-gates"><img src="https://agentmods.dev/badge/commands/nikiforovall/lazyclaude/run-quality-gates.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.00014 | $0.00048 |
| Opus 5 | $0.00007 | $0.00024 |
| Sonnet 5 | $0.00003 | $0.00010 |
| Haiku 4.5 | $0.00001 | $0.00005 |
Grade A, and why
run-quality-gates 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 11d 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
Invoke the quality-gates skill to run linting, formatting, type checking, and tests.
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.
- 11d ago First seen · 7 lines · 14 tokens per session scan A e7e5b4a9f6b7
run-quality-gates is a command published in the GitHub repository NikiforovAll/lazyclaude (42 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 48 once invoked, about $0.0001 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 commands, from other repositories
add-agent
Add a new sub-agent to the current plugin for specialized tasks.
add-command
Add a new slash command to the current plugin.
add-skill
Add a new Skill to the current plugin with proper structure.
init
Scaffold a new Claude Code plugin with standard structure and starter files.
hello
Greet the user with a friendly, personalized message.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.