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 skills add NikiforovAll/lazyclaude --skill quality-gatesgit 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/skills/nikiforovall/lazyclaude/quality-gates)<a href="https://agentmods.dev/skills/nikiforovall/lazyclaude/quality-gates"><img src="https://agentmods.dev/badge/skills/nikiforovall/lazyclaude/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/skills/nikiforovall/lazyclaude/quality-gates"><img src="https://agentmods.dev/badge/skills/nikiforovall/lazyclaude/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.00068 | $0.00378 |
| Opus 5 | $0.00034 | $0.00189 |
| Sonnet 5 | $0.00014 | $0.00076 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
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
Quality Gates
Run code quality checks for the lazyclaude project. This skill executes the same checks used in pre-commit hooks plus tests.
Quality Checks
The following checks are run in order:
| Check | Command | Purpose |
|---|---|---|
| Ruff Lint | uv run ruff check src tests --fix |
Lint code and auto-fix issues |
| Ruff Format | uv run ruff format src tests |
Format code consistently |
| Mypy | uv run mypy src |
Static type checking |
| Pytest | uv run pytest tests/ -q |
Run test suite |
Usage
To run all quality gates:
.claude/skills/quality-gates/scripts/check.sh
Or run individual checks as needed using the commands above.
Workflow
- Run the
.claude/skills/quality-gates/scripts/check.shscript from the project root - Review any failures and fix issues
- Re-run until all checks pass
- Present user with concise summary of results in markdown table format
Common Issues
- Ruff lint failures: Usually auto-fixed. If not, check the error message for manual fixes needed.
- Mypy errors: Type annotation issues. Add or fix type hints as indicated.
- Test failures: Review test output, fix failing tests or underlying code.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 43 lines · 68 tokens per session scan A 46178c29c79f
quality-gates is a skill published in the GitHub repository NikiforovAll/lazyclaude (42 stars, last pushed 5mo ago), licensed MIT. It adds 68 tokens to every session and 378 once invoked, about $0.0003 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 skills, from other repositories
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
e2e
Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".
tdd-cycle
Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".