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/rtk-ai/rtk/test-routinggit clone --depth 1 https://github.com/rtk-ai/rtkWhat 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.00017 | $0.02225 |
| Opus 5 | $0.00009 | $0.01112 |
| Sonnet 5 | $0.00003 | $0.00445 |
| Haiku 4.5 | $0.00002 | $0.00222 |
Grade A, and why
test-routing 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 — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test-routing
Vérifie le routing de commandes RTK sans exécution (dry-run). Utile pour tester si une commande a un filtre disponible avant de l'exécuter.
Usage
/test-routing <command> [args...]
Exemples
/test-routing git status
# Output: ✅ RTK filter available: git status → rtk git status
/test-routing npm install
# Output: ⚠️ No RTK filter, would execute raw: npm install
/test-routing cargo test
# Output: ✅ RTK filter available: cargo test → rtk cargo test
Quand utiliser
- Avant d'exécuter une commande: Vérifier si RTK a un filtre
- Debugging hook integration: Tester le command routing sans side-effects
- Documentation: Identifier quelles commandes RTK supporte
- Testing: Valider routing logic sans exécuter de vraies commandes
Implémentation
Option 1: Check RTK Help Output
COMMAND="$1"
shift
ARGS="$@"
# Check if RTK has subcommand for this command
if rtk --help | grep -E "^ $COMMAND" >/dev/null 2>&1; then
echo "✅ RTK filter available: $COMMAND $ARGS → rtk $COMMAND $ARGS"
echo ""
echo "Expected behavior:"
echo " - Command will be filtered through RTK"
echo " - Output condensed for token efficiency"
echo " - Exit code preserved from original command"
else
echo "⚠️ No RTK filter available, would execute raw: $COMMAND $ARGS"
echo ""
echo "Expected behavior:"
echo " - Command executed without RTK filtering"
echo " - Full command output (no token savings)"
echo " - Original command behavior unchanged"
fi
Option 2: Check RTK Source Code
COMMAND="$1"
shift
ARGS="$@"
# List of supported RTK commands (from src/main.rs)
RTK_COMMANDS=(
"git"
"grep"
"ls"
"read"
"err"
"test"
"log"
"json"
"lint"
"tsc"
"next"
"prettier"
"playwright"
"prisma"
"gh"
"vitest"
"pnpm"
"ruff"
"pytest"
"pip"
"go"
"golangci-lint"
"docker"
"cargo"
"smart"
"summary"
"diff"
"env"
"discover"
"gain"
"proxy"
)
# Check if command in supported list
if [[ " ${RTK_COMMANDS[@]} " =~ " ${COMMAND} " ]]; then
echo "✅ RTK filter available: $COMMAND $ARGS → rtk $COMMAND $ARGS"
echo ""
# Show filter details if available
case "$COMMAND" in
git)
echo "Filter: git operations (status, log, diff, etc.)"
echo "Token savings: 60-80% depending on subcommand"
;;
cargo)
echo "Filter: cargo build/test/clippy output"
echo "Token savings: 80-90% (failures only for tests)"
;;
gh)
echo "Filter: GitHub CLI (pr, issue, run)"
echo "Token savings: 26-87% depending on subcommand"
;;
pnpm)
echo "Filter: pnpm package manager"
echo "Token savings: 70-90% (dependency trees)"
;;
*)
echo "Filter: Available for $COMMAND"
echo "Token savings: 60-90% (typical)"
;;
esac
else
echo "⚠️ No RTK filter available, would execute raw: $COMMAND $ARGS"
echo ""
echo "Note: You can still use 'rtk proxy $COMMAND $ARGS' to:"
echo " - Execute command without filtering"
echo " - Track usage in 'rtk gain --history'"
echo " - Measure potential for new filter development"
fi
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 · 363 lines · 17 tokens per session scan A 867700ae99f1
test-routing is a command published in the GitHub repository rtk-ai/rtk (78,131 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 2,225 once invoked, about $0.0001 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-30.
Other commands, from other repositories
boldguy-linkedin-answer
Draft a LinkedIn comment on a post, referencing the guide's relevant section, in Flow style with AI markers removed.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
worktree
Create a git worktree for isolated feature/fix work.
sync
Check guide/landing synchronization status.
version
Display current guide and Claude Code versions.