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.
npx agentmods add commands/stefanhoelzl/codehydra/cigit clone --depth 1 https://github.com/stefanhoelzl/codehydraWrote 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/stefanhoelzl/codehydra/ci)<a href="https://agentmods.dev/commands/stefanhoelzl/codehydra/ci"><img src="https://agentmods.dev/badge/commands/stefanhoelzl/codehydra/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 | $0.00006 | $0.00158 |
| Opus 5 | $0.00003 | $0.00079 |
| Sonnet 5 | $0.00001 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
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 3d 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
/ci Command
Push the current branch, trigger CI workflow, and wait for completion.
Execution
Run the CI script:
npx tsx .claude/commands/ci-wait.ts
Exit Codes
- 0: SUCCESS - CI passed
- 1: FAILED - CI failed (logs printed)
- 2: TIMEOUT - Still running after 15 minutes
Report
After the script completes, report the result to the user:
- On success: "CI passed"
- On failure: Include the failed job names and relevant error details from the output
- On timeout: "CI timed out after 15 minutes"
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.
- 3d ago First seen · 31 lines · 6 tokens per session scan A 93cc9ea71bf5
ci is a command published in the GitHub repository stefanhoelzl/codehydra (20 stars, last pushed 5d ago), licensed MIT. It adds 6 tokens to every session and 158 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
ship
Pre-deploy / pre-merge gate. Detect the stack first (look for package.json, pyproject.toml/setup.cfg, go.mod, Cargo.toml, Makefile) and run only the checks that actually exist — never assume a script (lint, build, migrate) is present. Report each item as pass / fail / N/A.
release
You are a release agent for the Gigacode project (sandbox-agent). Your job is to cut a new release by running the release script, monitoring the GitHub Actions workflow, and fixing any failures until the release succeeds.
docs-builder
Reorg a docs corpus, split an oversized doc, search it, keep pages current, index them.
live-canvas
Conduct design interviews, generate UI variations, and collect live click-to-annotate feedback that streams into the session so edits land without leaving the browser. Use when the user wants rapid iterative UI refinement, not just batched feedback.
remember
Consolidate stashes + friction into project memory.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.