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.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)<a href="https://agentmods.dev/commands/plclub/hs-to-rocq/ci"><img src="https://agentmods.dev/badge/commands/plclub/hs-to-rocq/ci.svg" alt="Measured on agentmods" 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.00011 | $0.01310 |
| Opus 5 | $0.00005 | $0.00655 |
| Sonnet 5 | $0.00002 | $0.00262 |
| Haiku 4.5 | $0.00001 | $0.00131 |
Grade A, and why
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 6d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run CI checks locally, mirroring the GitHub Actions workflow in .github/workflows/hs-to-rocq.yml. Assume 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 must be 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.
Report pass/fail for each step. At the end, print a summary table of all steps and their results.
Job: build
stack build
Job: test-coq
Build all Coq targets in dependency order. For each directory, generate the Makefile from _CoqProject first:
# base
(cd base; coq_makefile -f _CoqProject -o Makefile) && make -j -C base
# base-thy
(cd base-thy; coq_makefile -f _CoqProject -o Makefile) && make -j -C base-thy
# 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
# transformers
(cd examples/transformers/lib; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/transformers/lib
# 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 HeapEquiv.vo Crush.vo Helper.vo NicerQueue.vo RealRing.vo Path.vo Lex.vo WeightedGraphs.vo
# 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
# core-semantics
(cd examples/core-semantics/lib; coq_makefile -f _CoqProject -o Makefile) && make -j -C examples/core-semantics/lib
# resources
coqc -Q base "" examples/resources/list_monad.v
Run each group sequentially (they depend on each other in order). Report pass/fail after each group.
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.
- 6d ago First seen · 146 lines · 11 tokens per session scan A 295044cdde0e
ci is a command published in the GitHub repository plclub/hs-to-rocq (96 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 1,310 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-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.
coverage-diff
Run the local diff-coverage check that mirrors CI's Diff coverage required gate.
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.