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.
git clone --depth 1 https://github.com/andycungkrinx91/konohaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/andycungkrinx91/konoha/rtk)<a href="https://agentmods.dev/rules/andycungkrinx91/konoha/rtk"><img src="https://agentmods.dev/badge/rules/andycungkrinx91/konoha/rtk/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/andycungkrinx91/konoha/rtk"><img src="https://agentmods.dev/badge/rules/andycungkrinx91/konoha/rtk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00332 | $0.00332 |
| Opus 5.5 | $0.00133 | $0.00133 |
| Sonnet 5.5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
rtk 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.
What it actually says
RTK - Rust Token Killer
Usage: Token-optimized CLI proxy for shell commands.
Mandatory Execution Rule
- Force-Run First with RTK: ALWAYS attempt and force-run every shell command with
rtk <command>first (e.g.rtk git status,rtk cargo test,rtk pnpm test,rtk python3 ...,rtk ls,rtk grep,rtk find,rtk docker ps). - Direct Shell / Bash Fallback: When RTK is not installed, not supported, or encounters an unrecognized command/syntax, immediately execute via direct shell/bash (
sh/bash).
Rule
Always prefix shell commands with rtk to minimize token consumption.
Examples:
rtk git status
rtk cargo test
rtk pnpm test
rtk ls src/
rtk grep "pattern" src/
rtk find "*.rs" .
rtk docker ps
rtk gh pr list
Meta Commands
rtk gain # Show token savings
rtk gain --history # Command history with savings
rtk discover # Find missed RTK opportunities
rtk proxy <cmd> # Run raw (no filtering, for debugging)
Why
RTK filters and compresses command output before it reaches the LLM context, cutting up to 90% of the bash output on common operations. Always force-run rtk <cmd> first, falling back to direct shell/bash when unsupported.
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 · 39 lines · 332 tokens per session scan A 03b4e020e1a4
rtk is a cursor rule published in the GitHub repository andycungkrinx91/konoha (13 stars, last pushed yesterday), licensed MIT. It adds 332 tokens to every session, about $0.0013 per session on Opus 5.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-10-29.
Other cursor rules, from other repositories
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.