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.
git clone --depth 1 https://github.com/CrashBytes/claude-role-skillsWrote 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/crashbytes/claude-role-skills/pipeline)<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/pipeline"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/pipeline/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/commands/crashbytes/claude-role-skills/pipeline"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/pipeline.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.00013 | $0.00409 |
| Opus 5 | $0.00006 | $0.00204 |
| Sonnet 5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
pipeline 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 8d 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 Generator
Generate a production-ready CI/CD pipeline configuration.
Arguments
Platform and stack: $ARGUMENTS
Context
Project files: !ls package.json requirements.txt Gemfile go.mod Cargo.toml pom.xml build.gradle composer.json 2>/dev/null || echo "No package files detected"
Workflow
-
Detect platform and stack
- If platform is specified (github/gitlab), use it
- If not, check for existing
.github/workflows/or.gitlab-ci.yml - Auto-detect language from package files in the project root
-
Design pipeline stages
- Build: Install dependencies, compile if needed
- Lint: Code style and static analysis
- Test: Unit tests with coverage reporting
- Security: Dependency audit, SAST scan
- Deploy Staging: Deploy to staging environment
- Deploy Production: Deploy to production with approval gate
-
Apply best practices
- Cache dependencies between runs
- Run lint and test in parallel
- Use matrix builds for multiple versions where applicable
- Pin action/image versions (no
latesttags) - Use environment secrets (never hardcode)
- Add concurrency controls to prevent duplicate deployments
- Set appropriate timeouts
-
Configure deployment strategy
- Staging: auto-deploy on push to main
- Production: manual approval or tag-based trigger
- Include rollback instructions in comments
-
Output
- Complete pipeline YAML file
- Explanation of each stage
- Required secrets and environment variables to configure
- Instructions for first-time setup
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.
- 8d ago First seen · 53 lines · 0 tokens per session scan A b08f5cdff190
pipeline is a command published in the GitHub repository CrashBytes/claude-role-skills (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 409 once invoked, about $0.0001 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
launch-meta-campaign
Launch a complete Meta Ads campaign — campaign, ad set, and ad(s) — built paused and ready to review. Use when the user wants a new Facebook/Instagram campaign.
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
duck-off
Turn off Rubber Duck mode and answer normally.
triage
Promote ideas from Ideas.md into Epics or User Stories in the Epic backlog (dedup, typed ID, voice).
deploy
Deploy safely with multi-gate pipeline — test → build → stage → verify → production.
bug
Report a bug instantly to the bug Inbox (append-only, any language, safe mid-work).