Borrowing it
Nothing to install: this file belongs to plclub/hs-to-rocq. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/plclub/hs-to-rocq/master/.claude/commands/ci-fix.mdgit clone --depth 1 https://github.com/plclub/hs-to-rocqWrote 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/plclub/hs-to-rocq/ci-fix)<a href="https://agentmods.dev/commands/plclub/hs-to-rocq/ci-fix"><img src="https://agentmods.dev/badge/commands/plclub/hs-to-rocq/ci-fix/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/plclub/hs-to-rocq/ci-fix"><img src="https://agentmods.dev/badge/commands/plclub/hs-to-rocq/ci-fix.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.00044 | $0.02517 |
| Opus 5 | $0.00022 | $0.01259 |
| Sonnet 5 | $0.00009 | $0.00503 |
| Haiku 4.5 | $0.00004 | $0.00252 |
Grade A, and why
ci-fix 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 7d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run CI checks locally (mirroring .github/workflows/hs-to-rocq.yml), diagnose and fix any failures, then commit the fixes. All tools (stack, coqc, coq_makefile) are already installed — no Docker or opam setup needed. Do NOT use --allow-different-user (that's only for CI containers).
All commands run from the workspace root using relative paths.
The argument is: $ARGUMENTS
If the argument is empty or "all", run ALL four jobs in order. Otherwise run only the specified job.
Workflow
For each job:
- Run the CI step
- If it passes, move on
- If it fails, diagnose the error, fix it, re-run to verify, then continue
- After all jobs pass, commit any changes made during fixing
Keep an intervention log at .claude/ci-fix-log.md documenting each failure and how it was fixed. This helps track what went wrong and why.
Job: build
stack build
If it fails: Read the compiler error carefully. The Haskell source is in src/. Fix the compilation error, re-run stack build to verify.
Job: test-coq
Build all Coq targets in dependency order. For each directory, generate the Makefile from _CoqProject first. Run each group sequentially — they depend on each other in order.
# 1. base + base-thy
(cd base; coq_makefile -f _CoqProject -o Makefile) && make -j -C base
(cd base-thy; coq_makefile -f _CoqProject -o Makefile) && make -j -C base-thy
# 2. containers
(cd examples/containers/lib; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/containers/lib
(cd examples/containers/theories; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/containers/theories
# 3. transformers
(cd examples/transformers/lib; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/transformers/lib
# 4. graph
(cd examples/graph/lib; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/graph/lib
(cd examples/graph/theories; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/graph/theories
# 5. ghc
(cd examples/ghc/lib; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/ghc/lib
(cd examples/ghc/theories; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/ghc/theories
# 6. core-semantics
(cd examples/core-semantics/lib; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/core-semantics/lib
# 7. resources
coqc -Q base "" examples/resources/list_monad.v
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.
- 7d ago First seen · 204 lines · 44 tokens per session scan A 5c37245b0c46
ci-fix is a command published in the GitHub repository plclub/hs-to-rocq (96 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 2,517 once invoked, about $0.0002 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 commands, from other repositories
ci-setup
Setup CI pipeline from scratch. Creates GitHub Actions or GitLab CI configuration with lint, test, build, and deploy stages.
ship
Mechanical pre-deploy gate — tests, build, tree state.
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.…
ship
Before merging or deploying, run ALL of the following checks. Every gate must pass.
test-setup
Scaffold test framework and CI pipeline.
verify
Runs the fastest possible verification for changed stacks. Returns binary PASS/FAIL with counts.