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 Plazmodium/odin-workflow --skill ci-cd-and-automationgit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote 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/plazmodium/odin-workflow/ci-cd-and-automation)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/ci-cd-and-automation/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/plazmodium/odin-workflow/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/ci-cd-and-automation.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.00025 | $0.00308 |
| Opus 5 | $0.00013 | $0.00154 |
| Sonnet 5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
ci-cd-and-automation 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-and-automation
When To Use
- Creating or modifying CI, build, deploy, release, or automation workflows.
- A change needs automated quality gates.
- Deployment and release should be decoupled.
Workflow
- Identify the pipeline goal and triggering events.
- Move cheap checks early: format, lint, typecheck, unit tests, dependency checks.
- Keep slow or expensive checks later and conditional where appropriate.
- Fail fast with actionable logs.
- Use feature flags or staged rollout when deployment should not equal release.
- Protect secrets and least-privilege credentials.
- Verify locally when possible and document any unverified remote behavior.
Anti-Rationalization
| Excuse | Rebuttal |
|---|---|
| "CI will catch it later." | Shift Left: catch cheap failures before expensive stages. |
| "Deploying means released." | Decouple deploy from release when risk warrants flags. |
| "The workflow syntax looks right." | Pipelines need validation or a dry run where feasible. |
Verification
- Pipeline changes have syntax or dry-run validation where available.
- Quality gates map to project risk.
- Secrets and permissions are reviewed.
Exit Criteria
- Automation fails quickly, safely, and with useful evidence.
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 · 43 lines · 25 tokens per session scan A e46b80f512e4
ci-cd-and-automation is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 308 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-09-01.
Other skills, from other repositories
cicd-pipeline
Design and configure CI/CD pipelines with GitHub Actions, GitLab CI, and Forgejo Actions. Use this skill when the user asks to create a new workflow, set up pipeline triggers, configure caching or matrix builds, manage CI secrets, troubleshoot pipeline failures, or compare pipeline platforms — even if they don't say…
b123d-modeling
Use this skill when asked to model, build, or modify a 3D part or assembly with build123d — from a text description, a technical drawing (image or PDF), dimensions in a spec, or an existing STEP/STL file.
securing-github-actions-workflows
This skill covers hardening GitHub Actions workflows against supply chain attacks, credential theft, and privilege escalation. It addresses pinning actions to SHA digests, minimizing GITHUBTOKEN permissions, protecting secrets from exfiltration, preventing script injection in workflow expressions, and implementing…
cloudflare-ops
Cloudflare Workers + Wrangler edge ops: runtime, bindings, local dev, secrets, deploy/CI, Pages-vs-Workers. Triggers on: cloudflare workers, wrangler, wrangler deploy, wrangler.toml, KV, D1, R2, durable objects, queues, vectorize, compatibilitydate, edge functions, illegal invocation, waitUntil, caches API, smart…
ci-cd-ops
CI/CD pipeline patterns with GitHub Actions, release automation, and testing strategies. Use for: github actions, workflow, CI, CD, pipeline, deploy, release, semantic release, changesets, goreleaser, matrix, cache, secrets, environment, artifact, reusable workflow, composite action.
quality-tools
Outils de qualité - Atoll Tourisme. Use when setting up quality tools or CI.