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/HoangYell/markdy-comWrote 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/hoangyell/markdy-com/repair-diagram)<a href="https://agentmods.dev/commands/hoangyell/markdy-com/repair-diagram"><img src="https://agentmods.dev/badge/commands/hoangyell/markdy-com/repair-diagram/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/hoangyell/markdy-com/repair-diagram"><img src="https://agentmods.dev/badge/commands/hoangyell/markdy-com/repair-diagram.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.00027 | $0.00121 |
| Opus 5 | $0.00014 | $0.00060 |
| Sonnet 5 | $0.00005 | $0.00024 |
| Haiku 4.5 | $0.00003 | $0.00012 |
Grade A, and why
repair-diagram 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 10d 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
Repair Markdy Diagram
When running /repair-diagram:
- Read the active
.markdyor.mdyfile. - Run
diagnose_markdy_syntaxon the file content. - If syntax or architectural issues are detected, invoke
fix_markdy_codeto generate clean, auto-repaired code. - Replace the file content with the repaired version and summarize all resolved issues.
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.
- 10d ago First seen · 13 lines · 27 tokens per session scan A 8cd2d9e1844c
repair-diagram is a command published in the GitHub repository HoangYell/markdy-com (93 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 121 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
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
speckit.companion.doctor
Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
debug
Debug code issues with systematic problem-solving and troubleshooting steps.
performance
Diagnose or fix Bun/TypeScript performance. Loads the performance skill, then works the task through its workflow.
build-fix
A command that incrementally fixes TypeScript and build errors by running the project build, grouping and explaining errors, applying fixes, and checking the result again.