Borrowing it
Nothing to install: this file belongs to coder/httpjail. 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/coder/httpjail/main/.claude/commands/ci.mdgit clone --depth 1 https://github.com/coder/httpjailWrote 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/coder/httpjail/ci)<a href="https://agentmods.dev/commands/coder/httpjail/ci"><img src="https://agentmods.dev/badge/commands/coder/httpjail/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/coder/httpjail/ci"><img src="https://agentmods.dev/badge/commands/coder/httpjail/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.00000 | $0.00092 |
| Opus 5.5 | $0.00000 | $0.00037 |
| Sonnet 5.5 | $0.00000 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
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 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
Commit working changes and push them to CI
Run cargo clippy -- -D warnings before pushing changes.
Also fetch the latest version of the base branch and merge it into the current branch.
Enter loop where you wait for CI to complete using ./scripts/wait-pr-checks.sh
(auto-detects PR from current branch), resolve issues, and return to user once
CI is green or a major decision is needed to resolve it.
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 · 10 lines · 0 tokens per session scan A 22c4be2c13dc
ci is a command published in the GitHub repository coder/httpjail (961 stars, last pushed 1mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 92 tokens. 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-11.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
issue-to-mr-setup
Create an automation that implements GitLab issues when a configurable trigger label is applied. Polls one or more projects deterministically, clones the default branch, starts one OpenHands conversation per label event, then commits, pushes, and opens the merge request itself.
ship
Deploy feature through automated staging validation to production with rollback testing.
run-plan
Execute implementation plan phases for a change.
deploy
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.