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/igoruehara/spec-driven/setup-cinpx skills add igoruehara/spec-driven --skill setup-cigit clone --depth 1 https://github.com/igoruehara/spec-drivenWhat 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.00112 | $0.00627 |
| Opus 5 | $0.00056 | $0.00313 |
| Sonnet 5 | $0.00022 | $0.00125 |
| Haiku 4.5 | $0.00011 | $0.00063 |
Grade A, and why
setup-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.
What it actually says
Skill: Setup de CI/CD (gates SDD na pipeline)
Materializa os gates SDD na esteira automática — é onde "documento que o time tenta seguir" vira "regra que o sistema garante". Idempotente: re-rodar ajusta a pipeline existente.
Descubra o alvo
- Detecte o provedor (GitHub Actions / GitLab CI / Bitbucket / outro) pelo repo e por
integrations.md. - Leia
docs/engineering/TESTING.md(comandos de gate) e o quality gate doCLAUDE.md(cobertura mínima).
Proponha a pipeline (confirme antes de gerar)
Estágios em ordem; falhar bloqueia o merge:
- Lint/format → 2. Análise estática (type-check + complexidade + SAST) → 3. Unidade →
4. Integração → 5. Aceite (um por
AC-N) → 6. Cobertura (mín. doCLAUDE.md). - Regra SDD: PR que altera código sem spec aprovada em
specs/→ falha (job que checa a presença/status da spec correspondente à mudança).
Evidência rastreável: publique cobertura e análise estática como artefatos do run (e, se o
provedor permitir, como check/comentário no PR). O resultado de qualidade fica anexado à mudança e
alimenta a tendência do /metricas.
Gere
- O arquivo da pipeline (
.github/workflows/*.yml/.gitlab-ci.yml) usando os comandos dedocs/engineering/TESTING.md— não invente comandos; reuse os de lá. - ⚠️ Sem segredos no arquivo — use os secrets do provedor. Confirme antes de escrever.
- Registre a escolha de pipeline como ADR se for estrutural; aponte em
docs/engineering/agentic-layer.md.
Próximo passo
Combine com /revisar-pr (gate humano/agente). Juntos cobrem review + automação: a CI garante
os testes/cobertura/spec; o /revisar-pr garante a conformidade de processo no PR/MR.
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 · 35 lines · 112 tokens per session scan A b457d50286e9
setup-ci is a skill published in the GitHub repository igoruehara/spec-driven (213 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 627 once invoked, about $0.0006 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-30.
Other skills, from other repositories
deploy-release-test
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow. Use only when asked to run the full deploy test suite or this workflow specifically from an internal vercel/next.js PR branch. Do not use for…
ci
A specialized skill for Gemini CLI that provides high-performance, fail-fast monitoring of GitHub Actions workflows and automated local verification of CI failures. It handles run discovery automatically—simply provide the branch name.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
playwright-devops
DevOps workflows for Playwright - CI failure analysis, workflow debugging, and release operations.
agentic-actions-auditor
Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches. AI agents running in CI/CD pipelines.