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 zircote-plugins/sdlc-quality --skill qualitygit clone --depth 1 https://github.com/zircote-plugins/sdlc-qualityWrote 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/zircote-plugins/sdlc-quality/quality)<a href="https://agentmods.dev/skills/zircote-plugins/sdlc-quality/quality"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/quality/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/zircote-plugins/sdlc-quality/quality"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/quality.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.00074 | $0.01404 |
| Opus 5.5 | $0.00030 | $0.00562 |
| Sonnet 5.5 | $0.00015 | $0.00281 |
| Haiku 4.5 | $0.00007 | $0.00140 |
Grade A, and why
quality 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.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Standards
Guidance for implementing code quality requirements including formatting, linting, error handling, and documentation.
Tooling
Available Tools: If using Claude Code, the
pr-review-toolkit:code-revieweragent can assess code quality against these standards. Use/pr-review-toolkit:review-prfor comprehensive PR review.
Formatting Requirements
Automated Formatting (MUST)
- All source code MUST pass automated formatting checks before merge
- Projects MUST define and commit formatting configuration files
- Import/include statements MUST be automatically sorted and grouped
Formatting Standards (MUST)
| Standard | Requirement |
|---|---|
| Line length | MUST be 100 characters maximum |
| Indentation | MUST be consistent (spaces or tabs, not mixed) |
| Line endings | MUST be Unix-style (LF) |
| Trailing whitespace | MUST be removed |
| Final newline | MUST be present |
Formatter Configuration by Language
| Language | Tool | Config File |
|---|---|---|
| Rust | rustfmt | rustfmt.toml |
| TypeScript/JS | Prettier | .prettierrc |
| Python | Black/Ruff | pyproject.toml |
| Java | google-java-format | .editorconfig |
| Go | gofmt | (built-in) |
Linting Requirements
Static Analysis (MUST)
- Projects MUST use static analysis tools appropriate to the language
- CI pipelines MUST run linting with warnings treated as errors
- Lint rule exceptions MUST be documented with justification
Lint Categories
| Category | Enforcement |
|---|---|
| Correctness | MUST be enabled |
| Performance | MUST be enabled |
| Style | SHOULD be enabled |
| Complexity | SHOULD be enabled |
| Documentation | SHOULD be enabled |
| Pedantic | SHOULD be enabled |
| Nursery/Experimental | MAY be enabled |
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 · 206 lines · 74 tokens per session scan A eb2e3c87a156
quality is a skill published in the GitHub repository zircote-plugins/sdlc-quality (11 stars, last pushed 26d ago), licensed MIT. It adds 74 tokens to every session and 1,404 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 skills, from other repositories
dorodango
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
codebase-audit
A read-only method for auditing an entire codebase across contracts, data integrity, errors, security, architecture, technical debt, configuration, and caching. It produces prioritized findings and a repair roadmap.
codex-agent
Use when you want a second-opinion review via Codex CLI, cross-verification after another agent implements changes, debugging help, or alternative implementation proposals. Requires Codex CLI to be installed and authenticated.
project-health-auditor
Comprehensive codebase health analysis. Use when reviewing code quality, identifying technical debt, checking dependencies, or assessing project structure.
ring:using-assert
Using lib-observability/assert, Lerian's runtime assertion package, in two modes. Sweep Mode detects panic()/log.Fatal zero-panic violations, DIY invariant checks, hand-rolled domain predicates, and missing InitAssertionMetrics. Reference Mode catalogs the asserter lifecycle, domain predicates, observability trident…
ring:fixing-lint
Fixing lint to a clean state: runs the linter, groups reported issues into independent streams, and dispatches one parallel fixer agent per stream (ring:backend-go for Go, ring:general-purpose otherwise), iterating until clean. Use when a codebase has lint errors across multiple files. Skip for a single error (fix…