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 roodlicht/accans-sec-skills --skill cicd-hardeninggit clone --depth 1 https://github.com/roodlicht/accans-sec-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/skills/roodlicht/accans-sec-skills/cicd-hardening)<a href="https://agentmods.dev/skills/roodlicht/accans-sec-skills/cicd-hardening"><img src="https://agentmods.dev/badge/skills/roodlicht/accans-sec-skills/cicd-hardening/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/roodlicht/accans-sec-skills/cicd-hardening"><img src="https://agentmods.dev/badge/skills/roodlicht/accans-sec-skills/cicd-hardening.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.00061 | $0.03363 |
| Opus 5 | $0.00030 | $0.01682 |
| Sonnet 5 | $0.00012 | $0.00673 |
| Haiku 4.5 | $0.00006 | $0.00336 |
Grade B, and why
cicd-hardening scanned grade B with 1 finding 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 12d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
**Expression injection**. `${{ github.event.pull_request.title }}` directly in a `run:` block is command injection: a PR title with ``" ; rm -rf / #`` runs on the runner. Fix: pass the value via an env variable (`env: TI Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 12d ago First seen · 198 lines · 61 tokens per session scan B c849f7672400
cicd-hardening is a skill published in the GitHub repository roodlicht/accans-sec-skills (4 stars, last pushed 3mo ago), with no licence file. It adds 61 tokens to every session and 3,363 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
devsecops-checker
Review CI or CD pipeline configuration for DevSecOps controls and help Claude explain maturity gaps, missing safeguards, and practical improvements.
Supply Chain Security
Software supply chain security — SBOM generation and analysis, dependency confusion and typosquatting detection, malicious package indicators, CI/CD pipeline hardening, and artifact provenance/signing (SLSA, Sigstore).
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
building-patch-tuesday-response-process
Establish a structured operational process to triage, test, and deploy Microsoft Patch Tuesday security updates within risk-based remediation SLAs.
building-vulnerability-dashboard-with-defectdojo
Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.
usap-devsecops
DevSecOps pipeline security engineer (cs-devsecops-engineer). Use for pipeline security reviews, SAST/DAST result analysis, PR security gates, CI/CD hardening, supply chain risk, SBOM generation, or when the user says "pipeline security", "scan this PR", "CI/CD security", or "DevSecOps".