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/auto-setupgit 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.00044 | $0.00780 |
| Opus 5 | $0.00022 | $0.00390 |
| Sonnet 5 | $0.00009 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
auto-setup 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 2d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/auto-setup
Inspect the current project and propose configuration additions for the detected toolchain. Apply nothing without user approval at the end.
Step 1 — Detect
Check for these manifests in the project root and immediate subdirectories:
package.json→ Node.js / TypeScriptpyproject.toml,setup.py,requirements.txt,Pipfile→ PythonCargo.toml→ Rustgo.mod→ Gopom.xml,build.gradle→ JVM- Multiple of the above → Monorepo / mixed
For each detected stack, identify:
- Package manager (
npm/pnpm/yarn/poetry/pip/cargo/go/etc.) - Lint command (e.g.
npm run lint,ruff check,cargo clippy,golangci-lint run) - Typecheck command (e.g.
tsc --noEmit,mypy, none for Rust/Go which check at build) - Test command (e.g.
npm test,pytest,cargo test,go test ./...)
Read the actual scripts from package.json / pyproject.toml / etc. — don't assume names exist.
Step 2 — Propose CLAUDE.md additions
Show a diff block of what should be appended to the project's CLAUDE.md under a ## Project Toolchain heading:
## Project Toolchain
- **Stack:** <detected>
- **Lint:** `<command>`
- **Typecheck:** `<command>` (or "n/a — checked at build")
- **Test:** `<command>`
- **Run before commit:** `<lint && typecheck && test>`
Step 3 — Propose settings.json additions
If the project has .claude/settings.json, show a diff block adding permissions.allow entries for the detected commands so they don't prompt every time:
{
"permissions": {
"allow": [
"Bash(<lint command>)",
"Bash(<typecheck command>)",
"Bash(<test command>)"
]
}
}
Step 4 — Present and wait for approval
Output a single message containing:
- Detected: the stack(s) found and where (paths to manifests).
- Proposed CLAUDE.md addition: the markdown diff block from Step 2.
- Proposed settings.json addition: the JSON diff block from Step 3.
- Verification commands to run after applying (e.g.
<lint command>should exit 0 on a clean tree). - Ask: "Apply both changes? (yes / only CLAUDE.md / only settings.json / no)"
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.
- 2d ago First seen · 76 lines · 44 tokens per session scan A 6bd073ddf97f
auto-setup is a command published in the GitHub repository hautc-it/cil (1 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 780 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-08-31.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
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).
hunt
Active vulnerability hunt against a target by invoking tools/hunt.py (which calls vulnscanner.sh against recon/ /). Auto-runs recon first if no recon dir exists. Usage: /hunt target.com.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.