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/hautc-it/cil/developgit clone --depth 1 https://github.com/hautc-it/cilWhat 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.00022 | $0.00370 |
| Opus 5 | $0.00011 | $0.00185 |
| Sonnet 5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
develop 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 yesterday.
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
/develop $ARGUMENTS
1. Research
- If $ARGUMENTS is ambiguous, present 2–3 interpretations and confirm before proceeding.
- Read relevant files; map what already exists (Grep/Glob).
- Run
memory_search("$ARGUMENTS")ANDmemory_search("feedback")(replay prior corrections). - List assumptions explicitly. Define verifiable, concrete success criteria.
2. Feasibility — proceed only if total ≥ 35/50
| Dim | /10 | Notes |
|---|---|---|
| Scope clarity | well-defined? | |
| Pattern familiarity | similar code here? | |
| Dependency awareness | what does it touch? | |
| Edge cases | failure modes understood? | |
| Test strategy | how to verify? |
If < 35: return to Research and resolve gaps before planning.
3. Plan — block on user approval
Goal (one sentence) · Files to modify (with reason) · Files to create (with reason) · Steps (numbered, each independently completable) · Risks · Mitigations.
4. Implement
One step at a time. Verify after each unit. Touch only what's in the plan — no opportunistic refactors. If blocked or plan changes: stop and report, don't improvise.
5. Verify
Read diff vs plan · check each success criterion · scan adjacent code for regressions · run /review if changes are significant. Store key decisions: memory_store("decision", "what + why", ["$ARGUMENTS"]).
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.
- yesterday First seen · 33 lines · 22 tokens per session scan A 20d8d1d2a58d
develop is a command published in the GitHub repository hautc-it/cil (1 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 370 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-08-31.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
validate
Validate a finding — runs 7-Question Gate + 4-gate checklist. Kills weak findings before report writing. Prevents N/A submissions that hurt validity ratio. Usage: /validate.
convert-to-todowrite-tasklist-prompt
Purpose: Transform verbose, context-heavy slash commands into efficient TodoWrite tasklist-based methods with parallel subagent execution for 60-70% speed improvements.
security-audit
Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
session-end
I'll summarize this coding session and update the memory system with our accomplishments.