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 summarybotng/summarybot-ng --skill qcsd-cicd-swarmgit clone --depth 1 https://github.com/summarybotng/summarybot-ngWrote 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/summarybotng/summarybot-ng/qcsd-cicd-swarm)<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/qcsd-cicd-swarm"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/qcsd-cicd-swarm/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/summarybotng/summarybot-ng/qcsd-cicd-swarm"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/qcsd-cicd-swarm.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.00061 | $0.02412 |
| Opus 5 | $0.00030 | $0.01206 |
| Sonnet 5 | $0.00012 | $0.00482 |
| Haiku 4.5 | $0.00006 | $0.00241 |
Grade A, and why
qcsd-cicd-swarm 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 6d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QCSD CI/CD Swarm v1.0
Shift-left quality engineering swarm for CI/CD pipeline verification and release readiness.
Overview
The CI/CD Swarm takes code that passed Development quality checks and validates it is safe to release through the CI/CD pipeline. Where the Development Swarm asks "Is the code quality sufficient to ship?", the CI/CD Swarm asks "Is this change safe to release?"
This swarm operates at the pipeline level, analyzing test results, regression risk, flaky test impact, security pipeline status, and infrastructure changes to render a RELEASE / REMEDIATE / BLOCK decision.
QCSD Phase Positioning
| Phase | Swarm | Decision | When |
|---|---|---|---|
| Ideation | qcsd-ideation-swarm | GO / CONDITIONAL / NO-GO | PI/Sprint Planning |
| Refinement | qcsd-refinement-swarm | READY / CONDITIONAL / NOT-READY | Sprint Refinement |
| Development | qcsd-development-swarm | SHIP / CONDITIONAL / HOLD | During Sprint |
| Verification | qcsd-cicd-swarm | RELEASE / REMEDIATE / BLOCK | Pre-Release / CI-CD |
| Production | qcsd-production-swarm | HEALTHY / DEGRADED / CRITICAL | Post-Release |
Parameters
PIPELINE_ARTIFACTS: Path to CI/CD artifacts, test results, and build output (required, e.g.,ci/artifacts/)BASELINE_REF: Git ref for baseline comparison (optional, default:main)OUTPUT_FOLDER: Where to save reports (default:${PROJECT_ROOT}/Agentic QCSD/cicd/)DEPLOY_TARGET: Target deployment environment (optional, e.g.,staging,production)
ENFORCEMENT RULES - READ FIRST
| Rule | Enforcement |
|---|---|
| E1 | You MUST spawn ALL THREE core agents (qe-quality-gate, qe-regression-analyzer, qe-flaky-hunter) in Step 2. No exceptions. |
| E2 | You MUST put all parallel Task calls in a SINGLE message. |
| E3 | You MUST STOP and WAIT after each batch. No proceeding early. |
| E4 | You MUST spawn conditional agents if flags are TRUE. No skipping. |
| E5 | You MUST apply RELEASE/REMEDIATE/BLOCK logic exactly as specified in Step 5. |
| E6 | You MUST generate the full report structure. No abbreviated versions. |
| E7 | Each agent MUST read its reference files before analysis. |
| E8 | You MUST apply qe-deployment-advisor analysis on ALL pipeline data in Step 8. Always. |
| E9 | You MUST execute Step 7 learning persistence. No skipping. |
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/qcsd-cicd-swarm.yaml 4.8 KB
- schemas/output.json 2.7 KB
- scripts/validate-config.json 517 B
- steps/01-flag-detection.md 1.9 KB
- steps/02-core-agents.md 1.2 KB
- steps/03-batch1-results.md 533 B
- steps/04-conditional-agents.md 818 B
- steps/05-decision-synthesis.md 775 B
- steps/06-report-generation.md 509 B
- steps/07-learning-persistence.md 623 B
- steps/08-deployment-advisor.md 679 B
- steps/09-final-output.md 386 B
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.
- 6d ago First seen · 211 lines · 61 tokens per session scan A 3576f06db9ec
qcsd-cicd-swarm is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 2,412 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-09-03.
Other skills, from other repositories
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.
cicd-expert
Expert-level CI/CD with GitHub Actions, Jenkins, deployment pipelines, and automation. Use when the user mentions CI/CD, GitHub Actions, Jenkins, GitLab CI, deployment, or automation, or when the task involves CI/CD Fundamentals, Pipeline Design, Workflow Basics, or Docker Build and Push.
CI/CD Pipeline Config
CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.
ci-cd-pipeline
Design and implement CI/CD pipelines for automated testing and deployment.
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.