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/sanjar-x/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/sanjar-x/claudegram/health)<a href="https://agentmods.dev/commands/sanjar-x/claudegram/health"><img src="https://agentmods.dev/badge/commands/sanjar-x/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/sanjar-x/claudegram/health"><img src="https://agentmods.dev/badge/commands/sanjar-x/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.
Copies of this mod
1 near-identical copy found in the catalogue:
- health — 100% identical, 0 lines differ
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 sanjar-x/claudegram (3 stars, last pushed 6mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
debug
Systematic root-cause investigation, then fix with TDD — never proposes a fix before finding the cause; resumable diagnosis + regression test in .orc/ state. Workspace-aware. For a quick one-off look without session state, prefer the bundled /debug.
ccc-debug-session
Run a structured debug session: gather context, rank hypotheses, test them without editing code, then fix with a regression test and record the lesson. Use when a bug's cause is unclear.
ci
Diagnose and fix a red CI run — dispatches orc-ci-investigator, then routes on its verdict: auto-fix via orc-code-fixer, flake re-run, infra escalation, or /orc:debug hand-off.
bifrost-debug
Diagnose why the Bifrost gateway, memory injection, or skill discovery isn't working.
perf
Structured performance investigation with baselines, profiling, and evidence-backed decisions.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.