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/aj604/toolshedWrote 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/aj604/toolshed/doc-lifecycle)<a href="https://agentmods.dev/plugins/aj604/toolshed/doc-lifecycle"><img src="https://agentmods.dev/badge/plugins/aj604/toolshed/doc-lifecycle/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/aj604/toolshed/doc-lifecycle"><img src="https://agentmods.dev/badge/plugins/aj604/toolshed/doc-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
doc-lifecycle 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": "doc-lifecycle",
"version": "0.46.14",
"description": "Stop agents from acting on stale docs. Write README/CLAUDE.md/runbooks as checkable claims, grow the doc set only on demand signals, audit against the code with evidence-backed verdicts, and land fixes surgically \u2014 bootstrap \u2192 write \u2192 grow \u2192 detect \u2192 fix \u2192 prune/distill \u2192 schedule.",
"license": "MIT",
"homepage": "https://github.com/aj604/toolshed",
"repository": "https://github.com/aj604/toolshed",
"keywords": [
"documentation",
"docs",
"doc-drift",
"claude-code",
"skills",
"agents"
],
"author": {
"name": "Avery Jones",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 7 skills, 2 agents travel with it, and installing the plugin installs all of them — 962 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill scheduling-doc-sync A 96 tokens
- Skill detecting-doc-drift A 69 tokens
- Skill fixing-docs A 97 tokens
- Skill detecting-doc-bloat A 87 tokens
- Skill growing-docs A 140 tokens
- Skill writing-docs A 190 tokens
- Skill bootstrapping-docs A 125 tokens
- Agent doc-distiller A 83 tokens
- Agent llm-doc-writer A 75 tokens
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 · 21 lines scan A c2da71a5bfe6
doc-lifecycle is a plugin published in the GitHub repository aj604/toolshed (1 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
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…
han-communication
Foundational communication plugin for the Han suite. Owns the canonical readability standard, the writing-voice profile, and the explanation standard for talking to a reader who will not implement the work, plus the readability-guidance skill that surfaces the first two into a calling skill's own context for in-voice…
han-research
Pre-planning knowledge-work skills for the Han suite: understanding a problem before anyone commits to a plan. Home of research (research an open-ended question and end at an adversarially-validated recommendation), gap-analysis (compare two artifacts and report what is missing, incomplete, or conflicting), and…
shinkoku
A Claude Code plugin for Japanese tax filing. It supports employees with side businesses, including business-income, blue-return, income-tax, and consumption-tax filings.
ui-clone-skills
Motion forensics for the animated web. Four jobs against a live URL: decode (analyse motion + build, no code), clone (URL → React + Tailwind), verify (AE/SSIM + motion-parity score vs. an existing impl), extract (raw JSON dump). Extracts real CSS and animation params (GSAP / Framer Motion / Lenis / anime.js) directly…
sprint
Orchestrate staged milestones with native subagents on Claude Code or Oh My Pi, plus codex or mimo executors on Claude Code.