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/vincent-k2026/codachi/setupgit clone --depth 1 https://github.com/vincent-k2026/codachiWhat 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.00008 | $0.00225 |
| Opus 5 | $0.00004 | $0.00112 |
| Sonnet 5 | $0.00002 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade B, and why
setup scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
3. Read `~/.claude/settings.json` to check current statusline config What it actually says
Codachi Setup
You are setting up codachi as the user's Claude Code statusline.
Steps
- Determine the absolute path to the
dist/index.jsfile in this project - Test that the command works by running:
echo '{"model":{"display_name":"Test"},"context_window":{"used_percentage":50}}' | node <path>/dist/index.js - Read
~/.claude/settings.jsonto check current statusline config - Set the statusLine config:
{
"statusLine": {
"type": "command",
"command": "node <absolute-path-to>/dist/index.js"
}
}
- Tell the user to restart Claude Code for the pet to appear
Important
- Use the absolute path to dist/index.js
- Preserve any existing settings in settings.json
- If there's already a statusLine configured, warn the user before overwriting
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 · 32 lines · 8 tokens per session scan B bbccaecdaf5a
setup is a command published in the GitHub repository vincent-k2026/codachi (11 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 225 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
upgrade-nodejs
This guide explains how to upgrade the Node.js version that Bun reports for compatibility with Node.js packages and native addons.
upgrade-webkit
Upgrade Bun's WebKit fork to the latest upstream version of WebKit.
dedupe
Find duplicate GitHub issues.
code-review-checklist
Comprehensive checklist for conducting thorough code reviews to ensure quality, security, and maintainability.
memory-store
Store an insight, decision, or pattern to memory.
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).