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 aj604/toolshednpx agentmods add plugins/aj604/toolshed/doc-lifecyclegit clone --depth 1 https://github.com/aj604/toolshedGrade 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 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": "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 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 · 21 lines scan A c2da71a5bfe6
doc-lifecycle is a plugin published in the GitHub repository aj604/toolshed (2 stars, last pushed 25d 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
spec-forge
Generate and maintain professional software specifications — from idea validation to PRD, SRS, technical design, feature specs, test cases, review, audit, analysis, and propagation — based on industry standards.
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…
trigger-tree
See which docs your AI actually discovers — local documentation telemetry for Claude Code.
neatcontext
Save Claude Code work as reusable, domain-aware context.
rails-consultant
Plugin marketplace listing 1 plugin: rails-consultant.
rails-consultant
A collection of skills for Rails development and consulting, with an emphasis on learning, communication, and client success.