rtk is a command-line proxy that filters and compresses output from development commands before it reaches an LLM's context. It is used with coding agents to reduce the tokens consumed by commands such as Git operations. The catalogue includes skills, commands, agents, and instructions for using rtk in agent workflows.
Borrowing it
Nothing to install: this file belongs to rtk-ai/rtk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rtk-ai/rtk/develop/.claude/commands/diagnose.mdgit clone --depth 1 https://github.com/rtk-ai/rtkWrote 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/commands/rtk-ai/rtk/diagnose)<a href="https://agentmods.dev/commands/rtk-ai/rtk/diagnose"><img src="https://agentmods.dev/badge/commands/rtk-ai/rtk/diagnose/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/commands/rtk-ai/rtk/diagnose"><img src="https://agentmods.dev/badge/commands/rtk-ai/rtk/diagnose.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.00014 | $0.02723 |
| Opus 5.5 | $0.00006 | $0.01089 |
| Sonnet 5.5 | $0.00003 | $0.00545 |
| Haiku 4.5 | $0.00001 | $0.00272 |
Grade A, and why
diagnose 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 1mo 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/diagnose
Vérifie l'état de l'environnement RTK et suggère des corrections.
Quand utiliser
-
Automatiquement suggéré quand Claude détecte ces patterns d'erreur :
rtk: command not found→ RTK non installé ou pas dans PATH- Hook errors in Claude Code → Hooks mal configurés ou non exécutables
Unknown commanddans RTK → Version incompatible ou commande non supportée- Token savings reports missing →
rtk gainnot working - Command routing errors → Hook integration broken
-
Manuellement après installation, mise à jour RTK, ou si comportement suspect
Exécution
1. Vérifications parallèles
Lancer ces commandes en parallèle :
# RTK installation check
which rtk && rtk --version || echo "❌ RTK not found in PATH"
# Git status (verify working directory)
git status --short && git branch --show-current
# Hook configuration check
if [ -f ".claude/hooks/rtk-rewrite.sh" ]; then
echo "✅ OK: rtk-rewrite.sh hook present"
# Check if hook is executable
if [ -x ".claude/hooks/rtk-rewrite.sh" ]; then
echo "✅ OK: hook is executable"
else
echo "⚠️ WARNING: hook not executable (chmod +x needed)"
fi
else
echo "❌ MISSING: rtk-rewrite.sh hook"
fi
# Hook rtk-suggest.sh check
if [ -f ".claude/hooks/rtk-suggest.sh" ]; then
echo "✅ OK: rtk-suggest.sh hook present"
if [ -x ".claude/hooks/rtk-suggest.sh" ]; then
echo "✅ OK: hook is executable"
else
echo "⚠️ WARNING: hook not executable (chmod +x needed)"
fi
else
echo "❌ MISSING: rtk-suggest.sh hook"
fi
# Claude Code context check
if [ -n "$CLAUDE_CODE_HOOK_BASH_TEMPLATE" ]; then
echo "✅ OK: Running in Claude Code context"
echo " Hook env var set: CLAUDE_CODE_HOOK_BASH_TEMPLATE"
else
echo "⚠️ WARNING: Not running in Claude Code (hooks won't activate)"
echo " CLAUDE_CODE_HOOK_BASH_TEMPLATE not set"
fi
# Test command routing (dry-run)
if command -v rtk >/dev/null 2>&1; then
# Test if rtk gain works (validates install)
if rtk --help | grep -q "gain"; then
echo "✅ OK: rtk gain available"
else
echo "❌ MISSING: rtk gain command (old version or wrong binary)"
fi
else
echo "❌ RTK binary not found"
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.
- 1mo ago First seen · 353 lines · 14 tokens per session scan A c325af9e0d46
diagnose is a command published in the GitHub repository rtk-ai/rtk (84,655 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 2,723 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
subagent-diagnose
Multi-agent failure-investigation orchestrator. Parallel to /subagent-implementation — same scratchpad + investigator + builder/surgeon + reviewer + FOLLOWUPS pattern — but starts from a failure, not a spec. Two modes share one loop: ci (failed CI run is the brief seed) and bug (freeform symptom paragraph is the brief…
quick-fix
Implement→review subagent loop with no planning phase, for a fix whose cause is known and whose shape is obvious, however many files it touches. No spec, no worktree, no docs or signals at the end; one audit. Routes to /subagent-diagnose on an unknown cause and to /atomic-plan on an open approach or contract choice.
optimize
Suggest concrete performance improvements for the given file or directory.
dream
Overnight autoresearch + maintainer sweep that surfaces a MORNING REPORT — suggested changes, issues raised with fixes, and kept improvements. Shadow-first; never auto-pushes. Runs on-demand or scheduled for off-hours.
debloat
Retroactive whole-repo bloat removal (spec H-2ii). Scores an existing repo on the deterministic bloat axes, writes BLOAT-REPORT.md, and — only behind a passing test-suite safety oracle — proposes gated refactor waves as a PR. The zero-risk adoption hook.
maintain
Run automated maintenance — seeker finds bugs from pod logs and raises GitHub issues, fixer picks them up and creates PRs. Can run as a one-shot or scheduled via /schedule.