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 instructions/lexus2016/claude-code-studio/claude-mdgit clone --depth 1 https://github.com/Lexus2016/claude-code-studioWhat 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.17008 | $0.17008 |
| Opus 5 | $0.08504 | $0.08504 |
| Sonnet 5 | $0.03402 | $0.03402 |
| Haiku 4.5 | $0.01701 | $0.01701 |
Grade B, and why
claude-code-studio CLAUDE.md scanned grade B with 3 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Spreading `~/.claude/config.json` and `config.json` raw lets a local `model:""` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
that from a local `curl`, so a SHORT secret is spendable through one. That is the Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **The captures ride the CONTROL CLIENT, not `spawnSync`.** A control client answers The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 917 lines · 17,008 tokens per session scan B d60dccc59bfd
claude-code-studio CLAUDE.md is an instructions file published in the GitHub repository Lexus2016/claude-code-studio (133 stars, last pushed 5d ago), with no licence file. It adds 17,008 tokens to every session, about $0.0850 per session on Opus 5. A static security scan graded it B with 3 findings (reads agent configuration directories, makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
onedev AGENTS.md
AGENTS.md instructions for theonedev/onedev: Do not add Co-authored-by: or other co-author / AI attribution footers to commit messages unless the user explicitly asks for them. If such a trailer is injected into a commit you just created (and it is not pushed), rewrite the commit message to remove it before finishing.
veritas-kanban AGENTS.md
Instructions for BradGroux/veritas-kanban, covering agents.md — canonical agent instructions for veritas kanban, runtime requirements, repository layout, essential commands and install.
flux AGENTS.md
Instructions for sirsjg/flux, covering agents.md, project overview, dogfooding, common commands and development.
operator CLAUDE.md
Instructions for untra/operator, covering claude.md - operator, project overview, tech stack, code style and plans & specs location.
orbit CLAUDE.md
Instructions for Noveum/orbit, covering orbit, hard rules, bun is the toolchain, not the runtime, layout and commands.
FlowBoard AGENTS.md
Instructions for rasimme/FlowBoard, covering flowboard — agent entry point, start here and where things live.