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 setupgit 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/setup)<a href="https://agentmods.dev/skills/zircote-plugins/sdlc-quality/setup"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/setup/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/setup"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sdlc-quality/setup.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.00064 | $0.01874 |
| Opus 5.5 | $0.00026 | $0.00750 |
| Sonnet 5.5 | $0.00013 | $0.00375 |
| Haiku 4.5 | $0.00006 | $0.00187 |
Grade A, and why
setup 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Setup Standards
Guidance for initializing new projects that comply with all SDLC requirements from the start.
Tooling
Available Tools: If using Claude Code with the sdlc plugin, run
/sdlc:initto bootstrap a compliant project structure. The/sdlc:checkcommand validates existing projects.
Project Initialization
Required Steps (MUST)
New projects MUST complete these setup steps:
| Order | Step | Purpose |
|---|---|---|
| 1 | Create repository | Initialize Git with main branch |
| 2 | Add standard files | LICENSE, README, etc. |
| 3 | Configure build system | Makefile with standard targets |
| 4 | Set up CI pipeline | GitHub Actions workflow |
| 5 | Configure quality tools | Formatter, linter, etc. |
| 6 | Add security scanning | Dependency audit, secrets scan |
| 7 | Create documentation | README, CONTRIBUTING, etc. |
Repository Initialization
# Initialize repository
git init
git branch -M main
# Create standard directory structure
mkdir -p src tests docs .github/workflows
# Initialize with empty commit
git commit --allow-empty -m "chore: initialize repository"
Required Files
Mandatory Files (MUST)
Every project MUST include:
| File | Purpose | Template |
|---|---|---|
README.md |
Project overview | See docs skill |
LICENSE |
License terms | MIT, Apache-2.0, etc. |
CONTRIBUTING.md |
Contributor guide | See docs skill |
CHANGELOG.md |
Version history | Keep a Changelog |
SECURITY.md |
Security policy | See security skill |
.gitignore |
Git exclusions | Language-specific |
.gitattributes |
Git attributes | See vcs skill |
Makefile |
Build commands | See build skill |
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 · 344 lines · 64 tokens per session scan A 2ad0aa15d79a
setup is a skill published in the GitHub repository zircote-plugins/sdlc-quality (11 stars, last pushed 27d ago), licensed MIT. It adds 64 tokens to every session and 1,874 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
setup
Interactive project setup from the ai-project-template — replaces the static SETUPGUIDE.md with a guided, multi-step workflow.
template-guide
Navigate template conventions, audit compliance, and guide upgrades for ai-project-template repos.
cut-release
Cut a clean release — bump versions across all files, update changelog, create GitHub release.
merge-to-main
Babysit a PR through CI — create, monitor, fix failures, merge when green.
sota-devsecops
State-of-the-art DevSecOps and software supply chain security (2026). Applies when building or auditing CI/CD pipelines, GitHub Actions workflows, supply chain controls, SBOM generation, SAST/secret-scanning gates, dependency management, container builds, container/artifact registries, IaC (Terraform), GitOps…
repo-scaffold
Scaffold or standardize a production-ready repository structure with specs, source layout, tests, CI, agent context, config examples, release notes, and operational docs. Use when starting a new repo, turning a prototype into a maintainable project, adding missing repository foundations, or creating a repo skeleton…