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/dykyi-roman/awesome-claude-codeWrote 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/dykyi-roman/awesome-claude-code/audit-ci)<a href="https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/audit-ci"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/audit-ci/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/dykyi-roman/awesome-claude-code/audit-ci"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/audit-ci.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.00021 | $0.01447 |
| Opus 5 | $0.00010 | $0.00724 |
| Sonnet 5 | $0.00004 | $0.00289 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
audit-ci 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 5d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Audit
Perform a comprehensive audit of CI/CD configuration, including security, performance, and best practices.
Input Parsing
Parse $ARGUMENTS to extract path, level, and optional meta-instructions:
Format: [path] [level] [-- <meta-instructions>]
Arguments:
- path: Target directory (optional, default: ./)
- level: Audit depth - quick|standard|deep (optional, default: standard)
- -- meta-instructions: Additional focus areas or filters (optional)
Examples:
- /acc:audit-ci
- /acc:audit-ci ./
- /acc:audit-ci deep
- /acc:audit-ci ./ deep
- /acc:audit-ci -- focus on security
- /acc:audit-ci deep -- focus on security
- /acc:audit-ci -- level:deep (backward compatible)
Parsing rules:
- Split
$ARGUMENTSby--(space-dash-dash-space) - First part = positional arguments, Second part = meta-instructions
- In positional arguments, check if any word is a valid level (
quick|standard|deep) - If level found → extract it; remaining = path (or default
./) - Also accept
level:quick|standard|deepin meta-instructions (backward compatibility) - Priority: positional > meta-instruction > default (
standard)
Pre-flight Check
-
Find CI artifacts:
# CI configurations find . -name "*.yml" -path "*/.github/*" 2>/dev/null ls .gitlab-ci.yml 2>/dev/null # Docker files ls Dockerfile* 2>/dev/null # Static analysis configs ls phpstan.neon* psalm.xml* .php-cs-fixer* deptrac.yaml* 2>/dev/null # Test config ls phpunit.xml* 2>/dev/null -
If no CI found:
- Report "No CI configuration found"
- Suggest
/acc:ci-setup
Instructions
Use the acc:ci-coordinator agent to perform the audit:
Task tool with subagent_type="acc:ci-coordinator"
prompt: "Perform comprehensive CI/CD audit at [PATH]. Audit level: [LEVEL].
Operation: AUDIT
[FOCUS_AREAS if provided]
Use TaskCreate/TaskUpdate for progress visibility. Create tasks for each audit phase.
Audit areas:
1. Pipeline structure and stages
2. Static analysis configuration
3. Test configuration and coverage
4. Security (secrets, permissions, dependencies)
5. Performance (caching, parallelization)
6. Docker configuration
7. Deployment configuration
Generate a full audit report with:
- Summary by category
- Issues by severity
- Specific recommendations
- Action items"
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.
- 5d ago First seen · 235 lines · 0 tokens per session scan A 9929b70602ca
audit-ci is a command published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 23d ago), licensed MIT. It adds 21 tokens to every session and 1,447 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-03.
Other commands, from other repositories
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.