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/Uri6407/claudegramWrote 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/uri6407/claudegram/health)<a href="https://agentmods.dev/commands/uri6407/claudegram/health"><img src="https://agentmods.dev/badge/commands/uri6407/claudegram/health/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/uri6407/claudegram/health"><img src="https://agentmods.dev/badge/commands/uri6407/claudegram/health.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.00016 | $0.00168 |
| Opus 5.5 | $0.00006 | $0.00067 |
| Sonnet 5.5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
health 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.
This is a copy
100% identical to health — 0 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.
What it actually says
Покажи короткий отчёт о состоянии плагина:
mcp__plugin_claudegram_claudegram__health_check— connected/authorized/latency.mcp__plugin_claudegram_claudegram__get_server_version— версии claudegram/telethon/mcp/python.- Если
health_check.ok=false— покажиmessageи предложи fix.
Формат ответа: компактный markdown-блок без лишних рассуждений.
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 · 14 lines · 16 tokens per session scan A d8e30f54da91
health is a command published in the GitHub repository Uri6407/claudegram (2 stars, last pushed 16d ago), licensed MIT. It adds 16 tokens to every session and 168 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to health, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
reproduce-bug
Reproduce and investigate a bug using logs, console inspection, and browser screenshots.
verify-loop
A command that repeatedly checks recent code changes and tries to fix failures, with a configurable retry limit. It can run code review, builds, tests, linting, and type checks according to the project language.
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.
build-fix
A build-error fixing procedure for TypeScript projects. It runs the project build, groups and explains errors, applies fixes one at a time, and checks the build again.
simplify-transform
Apply verified simplifications with user approval. Part of simplify- family.
dead-code-report
Generate dead code findings report with implementation plan. Part of dead-code- family.