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/syf2211/ruledoctorWrote 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/plugins/syf2211/ruledoctor/plugin)<a href="https://agentmods.dev/plugins/syf2211/ruledoctor/plugin"><img src="https://agentmods.dev/badge/plugins/syf2211/ruledoctor/plugin/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/plugins/syf2211/ruledoctor/plugin"><img src="https://agentmods.dev/badge/plugins/syf2211/ruledoctor/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ruledoctor 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.
What it actually says
{
"name": "ruledoctor",
"version": "0.1.0",
"description": "RuleDoctor — reinject rules after compaction, block forbidden commands, and run session reports when the CLI is available.",
"author": {
"name": "syf2211",
"url": "https://github.com/syf2211/ruledoctor"
}
}
What it installs
The manifest is a name and a version. 1 skill, 3 hooks travel with it, and installing the plugin installs all of them — 105 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 10 lines scan A 425bfbc3ba0a
ruledoctor is a plugin published in the GitHub repository syf2211/ruledoctor (3 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-md-kit
Scaffold, audit and migrate CLAUDE.md files from inside Claude Code: /claude-md-new builds one from battle-tested templates using your repo's real commands; /claude-md-audit grades an existing one and returns worst-first fixes; /claude-md-migrate rewrites a bloated file into the lean verified style.
superpowers-zh
A Chinese-language plugin containing 20 AI coding skills, including translated and original workflows, for several coding-agent tools. Its listed topics include testing-driven development, debugging, and development practices.
multi-cursor
Official Cursor SDK coding harness.
project-brain
Folder structure + collaboration protocol so AI sessions can resume project context after compaction or window switch. One brain/ folder, 5 core files (PROJECT/MAP/STATUS/DECISIONS/HANDOFF), and a topic taxonomy.
documentation
Maintain project documentation maps, metadata and source inventories with portable scripts and staged Git checks.
memex
Zettelkasten-based agent memory system with bidirectional links.