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 skills/zircote-plugins/sdlc-quality/qualitynpx skills add zircote-plugins/sdlc-quality --skill qualitygit clone --depth 1 https://github.com/zircote-plugins/sdlc-qualityWhat 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.00074 | $0.01404 |
| Opus 5 | $0.00037 | $0.00702 |
| Sonnet 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 3d 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.
- 3d 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 (10 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 1,404 once invoked, about $0.0004 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 skills, from other repositories
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
bestie-features
Add BestieTemplate features (AGENTS.md, changelog, dependabot, pre-commit, lint workflow, testitem runner) to a Julia package with the bestie CLI — no Julia needed. Use when asked to add one of these files/setups to a package, or to see what BestieTemplate can add.
typescript-best-practices
Enforces TypeScript best practices and modern patterns.
verify-patterns
Verify AI agent patterns including loop safety, retry limits, tool consistency, context size, and graph cycle analysis. Use when asked to "verify agent patterns", "check loops", "verify tools", or "check retry limits".
rust-skills
Comprehensive Rust coding guidelines with 265 rules across 26 categories. Use when writing, reviewing, or refactoring Rust code. Covers ownership, error handling, async patterns, concurrency, unsafe code, API design, memory optimization, performance, numeric safety, conversions, serde, pattern matching, macros…
verify-language
Language-specific verification for Python, TypeScript/JavaScript, and Go. Checks type safety, language idioms, and best practices. Use when asked to "verify language", "check types", or for language-specific checks.