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 commands/srstomp/pokayokay/cicdgit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/commands/srstomp/pokayokay/cicd)<a href="https://agentmods.dev/commands/srstomp/pokayokay/cicd"><img src="https://agentmods.dev/badge/commands/srstomp/pokayokay/cicd.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.00009 | $0.00477 |
| Opus 5 | $0.00005 | $0.00238 |
| Sonnet 5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
cicd 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 3d 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
CI/CD Pipeline Workflow
Create, debug, or optimize CI/CD for: $ARGUMENTS
Steps
1. Detect Platform
Identify CI/CD platform from existing config:
.github/workflows/→ GitHub Actions.gitlab-ci.yml→ GitLab CI.circleci/config.yml→ CircleCIJenkinsfile→ Jenkinsazure-pipelines.yml→ Azure DevOps
If no config exists, ask which platform to use.
2. Identify Task Type
From $ARGUMENTS, determine the goal:
- Create: Generate new pipeline configuration
- Debug: Diagnose and fix pipeline failures
- Optimize: Improve build times and efficiency
- Deploy: Add deployment stages
- Review: Audit for best practices
3. Execute Task
For Creation:
- Design pipeline stages (build, test, deploy)
- Configure caching for dependencies
- Set up environment variables
- Add branch protection rules
For Debugging:
- Analyze failure logs
- Identify root cause
- Apply fix and test
For Optimization:
- Profile build times
- Add parallelization
- Configure caching
- Remove redundant steps
4. Create Implementation Tasks
npx @stevestomp/ohno-cli create "CI/CD: [specific improvement]" -t chore
Covers
- Pipeline creation and configuration
- Build optimization and caching
- Test parallelization
- Deployment strategies (rolling, blue-green, canary)
- Environment management
- Secret handling
Related Commands
/pokayokay:work- Implement pipeline changes/pokayokay:security- Audit pipeline security/pokayokay:observe- Add pipeline monitoring
Skill Integration
When CI/CD work involves:
- Security scanning → Also load
security-auditskill - Deployment monitoring → Also load
observabilityskill - Database migrations → Also load
database-designskill - Test optimization → Also load
testing-strategyskill
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.
- 3d ago First seen · 76 lines · 9 tokens per session scan A 749ad7d5f039
cicd is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 477 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.