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/Intense-Visions/harness-engineeringWrote 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/intense-visions/harness-engineering/cicd-fleet)<a href="https://agentmods.dev/commands/intense-visions/harness-engineering/cicd-fleet"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/cicd-fleet/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/intense-visions/harness-engineering/cicd-fleet"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/cicd-fleet.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.00091 | $0.00645 |
| Opus 5.5 | $0.00036 | $0.00258 |
| Sonnet 5.5 | $0.00018 | $0.00129 |
| Haiku 4.5 | $0.00009 | $0.00064 |
Grade A, and why
harness:cicd-fleet 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.
What it actually says
Phases:
- select: Enumerate red CI/CD runs and flaky-test signals via gh, classify each into the red-cause taxonomy (real-failure / flake / infra-config / already-green / needs-design), cross-check for already-green/superseded runs, and order remediable candidates by impact via roadmap-pilot scoring
- confirm: Present the triaged queue in one round — remediable items with their cause buckets, already-green items flagged for closure, needs-design items flagged to park, decision forks as questions, proposed concurrency — for a single up-front human approval
- dispatch: Fan out worktree-isolated subagents, each running the real harness-debugging (heal/deflake) or harness-workflow-audit (infra/config) pipeline for one item, capped at the concurrency governor; an un-deflakable flake or unforeseen fork parks and reports rather than hiding the failure
- verify: Independently confirm each returned branch has a plan artifact plus autopilot-state and is CI-green across all target operating systems plus the project's required checks — with deterministic repeated-run green for deflakes — never by subagent self-report
- report: Emit a one-row-per-item batch summary with remediation-actions notes for bulk human review, close already-green/superseded runs citing the resolving run/PR, and never merge
<execution_context> @agents/skills/claude-code/cicd-fleet/SKILL.md @agents/skills/claude-code/cicd-fleet/skill.yaml </execution_context>
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 · 41 lines · 91 tokens per session scan A 1b9cd2b1f8d2
harness:cicd-fleet is a command published in the GitHub repository Intense-Visions/harness-engineering (22 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 645 once invoked, about $0.0004 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-08-30.
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.
ci-setup
Setup CI pipeline from scratch. Creates GitHub Actions or GitLab CI configuration with lint, test, build, and deploy stages.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
004-harden-pm-verifier-production-harness
Make pm-verifier the one installable, versioned evaluation product in this repository. A clean checkout must support this complete loop without a second evaluation product.