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/ainpx skills add zircote-plugins/sdlc-quality --skill aigit 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/ai)<a href="https://agentmods.dev/skills/zircote-plugins/sdlc-quality/ai"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/ai.svg" alt="Measured on agentmods" 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 | $0.00067 | $0.01408 |
| Opus 5 | $0.00034 | $0.00704 |
| Sonnet 5 | $0.00013 | $0.00282 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
ai 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 4d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Assisted Development Standards
Guidance for implementing AI-assisted development requirements including context configuration, workflow integration, and quality practices.
Tooling
Available Tools: If using Claude Code, the
pr-review-toolkitprovides AI-powered code review agents. Thefeature-devplugin offers guided feature development workflows.
AI Context Configuration
Context Files (MUST)
Projects using AI assistants MUST maintain context files:
| File | Purpose | Location |
|---|---|---|
CLAUDE.md |
Claude-specific instructions | Repository root |
.cursorrules |
Cursor AI configuration | Repository root |
AI_CONTEXT.md |
Generic AI context | Repository root |
.github/copilot-instructions.md |
GitHub Copilot | .github/ |
Context File Content (MUST)
AI context files MUST include:
| Section | Content |
|---|---|
| Project overview | Brief description and purpose |
| Architecture | Key patterns and structures |
| Conventions | Naming, formatting, style rules |
| Constraints | What AI should NOT do |
| Key files | Important files to understand |
Context File Template
# Project Context for AI Assistants
## Overview
Brief project description and purpose.
## Architecture
- Pattern: [MVC/Clean Architecture/etc.]
- Key directories and their purposes
- Core abstractions
## Conventions
- Naming: camelCase for functions, PascalCase for types
- Error handling: Use Result types
- Testing: Unit tests alongside source
## Constraints
- Do NOT modify configuration files without asking
- Do NOT add new dependencies without approval
- Always run tests after changes
## Key Files
- `src/lib.rs` - Main library entry
- `src/config.rs` - Configuration handling
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.
- 4d ago First seen · 267 lines · 67 tokens per session scan A d141be768051
ai is a skill published in the GitHub repository zircote-plugins/sdlc-quality (10 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 1,408 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-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…
typescript-best-practices
Enforces TypeScript best practices and modern patterns.
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.
verify-quality
Verify code quality including naming conventions, organization, documentation, and general best practices. Use when asked to "verify quality", "check code quality", or "review code organization".
verify-security
Verify code for security issues including hardcoded secrets, input validation, error exposure, and dependency vulnerabilities. Use when asked to "verify security", "check for secrets", or "scan for vulnerabilities".
ai-agent-rules
This skill covers development patterns for the ai-agent-rules repository, a comprehensive collection of structured rules and guidelines for AI agent behavior. The repository focuses on maintaining consistent documentation standards, systematic rule organization, and automated synchronization workflows. It uses…