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/destynova2/cli-code-skills/cli-forge-pipelinenpx skills add Destynova2/cli-code-skills --skill cli-forge-pipelinegit clone --depth 1 https://github.com/Destynova2/cli-code-skillsWhat 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.00187 | $0.02840 |
| Opus 5 | $0.00093 | $0.01420 |
| Sonnet 5 | $0.00037 | $0.00568 |
| Haiku 4.5 | $0.00019 | $0.00284 |
Grade A, and why
cli-forge-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 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.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimization: This skill uses on-demand loading. Heavy content lives in
references/and is loaded only when needed.
Language rule: Skill instructions are written in English. When generating user-facing output (reports, files, documentation), detect the project's primary language (from README, comments, docs, commit messages) and produce the output in that language. If the project is bilingual, ask the user which language to use before proceeding.
CI Pipeline Optimizer — Biomimetic
"The leafcutter ant colony has no project manager. Yet it optimally relocates 15% of all tropical vegetation."
The 9 biological models → CI patterns
Read references/patterns.md for detailed explanations, biology, and dual GitLab/GitHub examples.
| # | Organism | CI Pattern | Key principle |
|---|---|---|---|
| 1 | Leafcutter ants (Atta) | Stage Specialization + Artifact Cache | Each job = one role. Artifacts = stigmergy |
| 2 | Slime mold (Physarum) | Change-Driven Path Selection + Cache Reinforcement | Only rerun what changed. Content-hashed cache |
| 3 | Army ants (Eciton) | Fan-out / Fan-in + Ephemeral Runners | Maximum parallelism, disposable runners |
| 4 | Honeybees (Apis) | Autoscaling + Priority-based Runner Tagging | Resources proportional to load |
| 5 | Mycelium | Multi-Registry Fallback + Distributed Cache | Zero SPOF, waterfall cache |
| 6 | Mitosis | Workflow Fission | Pipeline too big → split into independent workflows (S/M/L/XL semantics canonical in ../shared/tiering.md) |
| 7 | Immune system (VDJ) | Combinatorial Fuzzing + Property-Based Testing | Explore the input space, not just the known cases |
| 8 | Fungal spores | Full Combinatorial Matrix | OS × arch × version × features, fail-fast: false |
| 9 | Tardigrade | Chaos Engineering / Fault Injection | Inject failures to prove survival |
Workflow for analyzing an existing pipeline
Step 1 — Map the real DAG
Draw the actual dependencies. Identify sequential jobs that could run in parallel. Compute the critical path.
What ships with it
6 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.
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 · 220 lines · 187 tokens per session scan A f6d0b02d2f63
cli-forge-pipeline is a skill published in the GitHub repository Destynova2/cli-code-skills (5 stars, last pushed 11d ago), licensed MIT. It adds 187 tokens to every session and 2,840 once invoked, about $0.0009 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
pipeline-blueprint
Provide CI/CD best practices and pipeline templates for GitHub Actions and GitLab CI, recommending configurations based on project type (frontend, backend, fullstack, library, monorepo, mobile). Trigger when users ask about setting up CI/CD, automating builds, improving pipelines, or mention keywords like GitHub…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
fix-gh-actions
Investigate and fix failing GitHub Actions checks for this repo or its PRs. Use when the user asks to debug CI failures, broken workflows, failed release jobs, or failing GitHub checks.
github-action-review
Review fallow's GitHub Action, shell scripts, jq filters, annotations, review comments, and workflow integration. Use when changes touch action/, action.yml, GitHub review formatting, or CI shell/jq behavior.
ci-formats-review
Review SARIF, CodeClimate, compact, markdown, badge, and other CI-facing output formats for correctness and integrator expectations. Use when changes affect machine-consumed report formats or CI presentation layers.
gitlab-ci-review
Review fallow's GitLab CI integration, scripts, jq filters, MR comments, and report formatting. Use when changes touch ci/ or GitLab-specific output behavior.