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/ihudak/ihudak-claude-pluginsWrote 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/ihudak/ihudak-claude-plugins/docs-workflows)<a href="https://agentmods.dev/plugins/ihudak/ihudak-claude-plugins/docs-workflows"><img src="https://agentmods.dev/badge/plugins/ihudak/ihudak-claude-plugins/docs-workflows/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/ihudak/ihudak-claude-plugins/docs-workflows"><img src="https://agentmods.dev/badge/plugins/ihudak/ihudak-claude-plugins/docs-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
docs-workflows 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 today.
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": "docs-workflows",
"version": "1.1.2",
"description": "Three commands for the documentation half of the dev-workflows pipeline: /document runs in direct mode (a one-shot prose edit on any repository, style-checked and nothing more) or in keyed mode, which reads a resolved PRD folder and its PR trail of implementation diffs, synthesises product documentation, and adds an Opus doc review gate; /docs-profile bootstraps or refreshes a documentation repository's machine-readable profile and CLAUDE.md guidance that /document consumes, as a reviewable PR; /release-notes drafts a destination-shaped release-notes entry (breaking change, feature update, or fix) from the same PRD folder, optionally grounded in PR diffs. Seven agents and twelve reference pages carry the docs-repo discovery, PR-diff summarising, doc planning, writing and review these three commands share. Depends on workflows-core and on prose-style for its style-check gate.",
"author": {
"name": "Ivan Gudak",
"email": "[email protected]"
},
"homepage": "https://github.com/ihudak/ihudak-claude-plugins/tree/main/plugins/docs-workflows",
"repository": "https://github.com/ihudak/ihudak-claude-plugins",
"license": "MIT",
"dependencies": [
"workflows-core",
"prose-style"
],
"keywords": [
"documentation",
"release-notes",
"docs-profile",
"product-docs",
"prd",
"style-check"
]
}
What it installs
The manifest is a name and a version. 1 skill, 3 commands, 7 agents travel with it, and installing the plugin installs all of them — 1,012 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill docs-frontmatter A 89 tokens
- Command document A 88 tokens
- Command release-notes A 63 tokens
- Command docs-profile A 99 tokens
- Agent doc-planner A 76 tokens
- Agent doc-reviewer A 59 tokens
- Agent diff-summarizer A 96 tokens
- Agent docs-style-checker A 137 tokens
- Agent release-notes-writer A 164 tokens
- Agent doc-location-finder A 76 tokens
- Agent doc-writer A 65 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.
- today First seen · 25 lines scan A 6aad4532aa61
docs-workflows is a plugin published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed yesterday), 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-09-09.
Other plugins, from other repositories
converters
Say "convert this PDF to Markdown" or "turn this into a branded deck" and it happens. Documents, images, and Outlook email go in; Markdown, HTML, Word, PowerPoint, and Excel come out.
import
Import external documentation locally - bypass AI-blocking sites via Context7, WebFetch, or Playwright.
doc
Multi-purpose documentation toolkit (generation, explanation, diagrams, RFCs, health).
canvas-design
Create beautiful visual art in PNG and PDF documents using design philosophy. Use for posters, art pieces, designs, or other static visual works with museum-quality craftsmanship.
review-gate
Native Claude Code AI code review + blocking pre-push gate on your Claude subscription. Isolated headless reviewer, severity/confidence verdicts, fails closed. open-code-review, done compliantly.
docs-generator
Document generation for writeups, tech specs (ADR/RFC/design docs), and reports with optional pandoc PDF export.