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.
/plugin marketplace add SectionTN/stale-docsnpx agentmods add plugins/sectiontn/stale-docs/marketplacegit clone --depth 1 https://github.com/SectionTN/stale-docsGrade A, and why
stale-docs 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 yesterday.
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": "stale-docs",
"owner": {
"name": "SectionTN",
"url": "https://github.com/SectionTN"
},
"metadata": {
"description": "Detects documentation made stale by code changes and patches it in the same commit."
},
"plugins": [
{
"name": "stale-docs",
"source": "./",
"description": "Detects documentation made stale by code changes and patches it in the same commit."
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 18 lines scan A 6d58347bcf51
stale-docs is a plugin published in the GitHub repository SectionTN/stale-docs (3 stars, last pushed 1mo 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-31.
Other plugins, from other repositories
akira-plugins
Claude Code plugins by akira993 — documentation audit and review tooling.
docaudit
Change-driven documentation audit harness with local check-docs onboarding, pre-flight checks, sealed run evidence, deterministic PASS caching, light/standard routing, delegated doc checks, and review-backed CONSISTENT / NEEDS FIX / REFUSED verdicts.
servicenow-docs
Live ServiceNow product documentation for Claude, read straight from ServiceNow's official docs repo.
servicenow-docs
Live, searchable access to ServiceNow's official AI Platform documentation. Reads the ServiceNowDocs repo's llms.txt index and fetches individual topic files on demand from GitHub - always current, no local clone required. Requires uv (a one-line install) so the bundled Fetch MCP server can start.
report-skill
A Claude Code skill that turns long-form agent output into a designed HTML report instead of a flat Markdown file.
report
Render long-form agent output as a designed HTML report — TOC, callouts, framed figures, footnotes, light/dark themes, in-document review comments, and lossless round-trip back to Markdown.