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/bronz3beard/ai.tech-lead-stack/claude-mdgit clone --depth 1 https://github.com/bronz3beard/ai.tech-lead-stackWhat 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.01335 | $0.01335 |
| Opus 5 | $0.00668 | $0.00668 |
| Sonnet 5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade C, and why
ai.tech-lead-stack CLAUDE.md scanned grade C with 2 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- rtk-instructions v2 --> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
rtk curl <url> # Compact HTTP responses (70%) This is a copy
89% identical to grit CLAUDE.md — 76 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@AGENTS.md
RTK (Rust Token Killer) - Token-Optimized Commands
Golden Rule
Always prefix commands with rtk. If RTK has a dedicated filter, it uses
it. If not, it passes through unchanged. This means RTK is always safe to use.
Important: Even in command chains with &&, use rtk:
# ❌ Wrong
git add . && git commit -m "msg" && git push
# ✅ Correct
rtk git add . && rtk git commit -m "msg" && rtk git push
RTK Commands by Workflow
Build & Compile (80-90% savings)
rtk cargo build # Cargo build output
rtk cargo check # Cargo check output
rtk cargo clippy # Clippy warnings grouped by file (80%)
rtk tsc # TypeScript errors grouped by file/code (83%)
rtk lint # ESLint/Biome violations grouped (84%)
rtk prettier --check # Files needing format only (70%)
rtk next build # Next.js build with route metrics (87%)
Test (90-99% savings)
rtk cargo test # Cargo test failures only (90%)
rtk vitest run # Vitest failures only (99.5%)
rtk playwright test # Playwright failures only (94%)
rtk test <cmd> # Generic test wrapper - failures only
Git (59-80% savings)
rtk git status # Compact status
rtk git log # Compact log (works with all git flags)
rtk git diff # Compact diff (80%)
rtk git show # Compact show (80%)
rtk git add # Ultra-compact confirmations (59%)
rtk git commit # Ultra-compact confirmations (59%)
rtk git push # Ultra-compact confirmations
rtk git pull # Ultra-compact confirmations
rtk git branch # Compact branch list
rtk git fetch # Compact fetch
rtk git stash # Compact stash
rtk git worktree # Compact worktree
Note: Git passthrough works for ALL subcommands, even those not explicitly listed.
GitHub (26-87% savings)
rtk gh pr view <num> # Compact PR view (87%)
rtk gh pr checks # Compact PR checks (79%)
rtk gh run list # Compact workflow runs (82%)
rtk gh issue list # Compact issue list (80%)
rtk gh api # Compact API responses (26%)
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 · 160 lines · 1,335 tokens per session scan C c1e8d7393683
ai.tech-lead-stack CLAUDE.md is an instructions file published in the GitHub repository bronz3beard/ai.tech-lead-stack (3 stars, last pushed 2d ago), licensed MIT. It adds 1,335 tokens to every session, about $0.0067 per session on Opus 5. A static security scan graded it C with 2 findings (hidden instructions, makes network calls). It is 89% identical to grit CLAUDE.md, differing in 76 lines, and is treated as a copy.
Other instructions, from other repositories
thinkrail AGENTS.md
Instructions for JetBrains/thinkrail, covering thinkrail, module structure & boundaries (top-priority requirement), engine: pi only, in-process, architecture (three rings) and repo layout.
raytsystem-public-os CLAUDE.md
Instructions for romarayt/raytsystem-public-os, covering compatibility pointer and documentation synchronization.
raytsystem-public-os AGENTS.md
Instructions for romarayt/raytsystem-public-os, covering raytsystem — agent routing, invariants, commands, skill routing and documentation.
examples CLAUDE.md
Claude Code instructions for rossoctl/examples, covering claude.md - agent examples, repository structure, key commands, code style and dco sign-off (mandatory).
pilot CLAUDE.md
Claude Code instructions for qf-studio/pilot, covering pilot: ai that ships your tickets, who is reading this file?, ⚠️ git & worktree discipline (all sessions), quick commands and plan a feature (navigator).
metatron CLAUDE.md
Instructions for kerbelp/metatron, covering claude.md, what metatron is, tech stack (decided — not open for debate), core principle and source of truth (depends on deployment).