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/ci-setup)<a href="https://agentmods.dev/commands/dykyi-roman/awesome-claude-code/ci-setup"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/ci-setup/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/ci-setup"><img src="https://agentmods.dev/badge/commands/dykyi-roman/awesome-claude-code/ci-setup.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.00026 | $0.00927 |
| Opus 5.5 | $0.00010 | $0.00371 |
| Sonnet 5.5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
ci-setup 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup CI Pipeline
Create a complete CI/CD pipeline for a PHP project from scratch.
Input Parsing
Parse $ARGUMENTS to extract platform, path, and optional meta-instructions:
Format: <platform> [path] [-- <meta-instructions>]
Examples:
- /acc:ci-setup github
- /acc:ci-setup gitlab ./
- /acc:ci-setup github ./src -- include Docker, blue-green deploy
- /acc:ci-setup gitlab -- skip deploy, focus on testing
Parsing rules:
- First argument = platform (
githuborgitlab) - Second argument = path (optional, defaults to
./) - After
--= meta-instructions (optional customization)
Pre-flight Check
-
Verify platform specified:
- If empty, ask user: "Which CI platform? (github/gitlab)"
-
Check existing CI:
ls -la .github/workflows/ 2>/dev/null ls -la .gitlab-ci.yml 2>/dev/null- Warn if CI already exists
- Ask to overwrite or extend
-
Analyze project:
cat composer.json | jq '.require.php, ."require-dev"' ls phpstan.neon* psalm.xml* .php-cs-fixer* 2>/dev/null ls phpunit.xml* 2>/dev/null ls Dockerfile* 2>/dev/null
Instructions
Use the acc:ci-coordinator agent to set up the CI pipeline:
Task tool with subagent_type="acc:ci-coordinator"
prompt: "Set up CI pipeline for [PATH].
Platform: [PLATFORM]
[META-INSTRUCTIONS if provided]
Operation: SETUP
Required components:
1. Pipeline workflow (lint, test, build)
2. Static analysis configs (PHPStan, Psalm, CS-Fixer)
3. Test configuration (PHPUnit)
4. Docker configuration (if needed)
5. Deployment configuration (if requested)
Analyze the project and generate all necessary files."
Expected Output
The coordinator will:
-
Analyze the project:
- PHP version
- Dependencies and dev tools
- Test framework
- Existing configurations
-
Generate CI workflow:
.github/workflows/ci.ymlor.gitlab-ci.yml- Stages: install, lint, test, build, deploy
-
Generate tool configs (if missing):
phpstan.neonpsalm.xml.php-cs-fixer.dist.phpdeptrac.yaml
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.
- 1mo ago First seen · 135 lines · 26 tokens per session scan A 0728ab9fbf89
ci-setup is a command published in the GitHub repository dykyi-roman/awesome-claude-code (105 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 927 once invoked, about $0.0001 per session on Opus 5.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
judge-ci-red
Load when: loom-daemon forge wait-checks printed LOOM-CHECKS-RED, or post-verdict.sh … approved exited 6, and a CI-failing verdict is next.
write-test-plan
Generate or update change test plan.
test-setup
Scaffold test framework and CI pipeline.
harness:cicd-fleet
Autonomous CI/CD-remediation orchestrator — triage the red CI/CD-run and flaky-test backlog by cause, fan out worktree-isolated subagents that run the real deflake/heal pipeline, independently verify each fix by artifact and deterministic all-OS CI, and hand back a batch of remediation PRs for one bulk human review.…
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
quality-check
Execute a comprehensive quality gate check (lint, test, build, format) before allowing code to merge.