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/cinpx skills add zircote-plugins/sdlc-quality --skill cigit 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.00060 | $0.01472 |
| Opus 5 | $0.00030 | $0.00736 |
| Sonnet 5 | $0.00012 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
ci 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 2d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Standards
Guidance for implementing compliant CI/CD pipelines that meet SDLC requirements.
Tooling
Available Tools: If using Claude Code, the
gh:ci-assistskill can help migrate and configure CI pipelines. Also seegh:migratefor CI/CD migration from other platforms.
Pipeline Trigger Requirements
When CI MUST Run
CI MUST run on:
- All pull requests to protected branches
- All pushes to protected branches (develop, main)
- Scheduled intervals (daily/weekly for security scans)
Concurrency Controls (MUST)
CI MUST implement concurrency controls to cancel superseded runs:
# GitHub Actions example
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
Required Pipeline Jobs
Job Order (MUST)
CI pipelines MUST include these jobs in order:
| Order | Job | Purpose | Required |
|---|---|---|---|
| 1 | Format check | Verify code formatting | MUST |
| 2 | Lint | Static analysis with errors | MUST |
| 3 | Test | Run all tests | MUST |
| 4 | Documentation | Verify docs build | MUST |
| 5 | Security audit | Check for vulnerabilities | MUST |
| 6 | MSV check | Verify minimum version support | MUST |
| 7 | Coverage | Measure test coverage | SHOULD |
| 8 | Benchmarks | Performance regression check | SHOULD |
All Jobs Must Pass (MUST)
All CI jobs MUST pass before a PR can be merged. Configure branch protection to enforce this.
CI Configuration Requirements
Pinned Action Versions (MUST)
CI workflows MUST use pinned action versions. Prefer commit SHAs over tags:
# Good - SHA pinned
- uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608 # v4.1.0
# Acceptable - tag pinned
- uses: actions/[email protected]
# Bad - floating tag
- uses: actions/checkout@v4
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.
- 2d ago First seen · 241 lines · 60 tokens per session scan A c2563f05a0eb
ci is a skill published in the GitHub repository zircote-plugins/sdlc-quality (10 stars, last pushed 29d ago), licensed MIT. It adds 60 tokens to every session and 1,472 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…
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.