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/nicepkg/ai-workflowWrote 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/nicepkg/ai-workflow/writing-product-specs)<a href="https://agentmods.dev/plugins/nicepkg/ai-workflow/writing-product-specs"><img src="https://agentmods.dev/badge/plugins/nicepkg/ai-workflow/writing-product-specs/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/nicepkg/ai-workflow/writing-product-specs"><img src="https://agentmods.dev/badge/plugins/nicepkg/ai-workflow/writing-product-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
writing-product-specs 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 2mo 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": "writing-product-specs",
"description": "Write comprehensive product specification documents that clearly communicate what we're building, why, and how we'll know it's successful",
"version": "1.0.0",
"author": {
"name": "Britt Crawford",
"email": "[email protected]"
},
"homepage": "https://github.com/britt/claude-code-skills",
"repository": "https://github.com/britt/claude-code-skills",
"license": "MIT",
"keywords": ["specs", "prd", "product", "requirements", "documentation"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 15 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.
- 2mo ago First seen · 14 lines scan A 4e5ae372f856
writing-product-specs is a plugin published in the GitHub repository nicepkg/ai-workflow (290 stars, last pushed 9mo 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-09-03.
writing-product-specs compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| writing-product-specsnicepkg/ai-workflow | Plugin | 290 | 9mo ago | MIT | A | — | Claude Code |
| headroom-skillheadroomlabs-ai/headroom | Plugin | 79k | yesterday | Apache-2.0 | A | — | Claude Code |
| robinlangchain-ai/open-swe | Plugin | 11k | yesterday | MIT | A | — | Claude Code |
| ensembleraiyanyahya/ensemble | Plugin | 13 | 5mo ago | MIT | A | — | Claude Code |
| humanizerblader/humanizer | Plugin | 65k | 10d ago | MIT | A | — | Claude Code |
| claude-plugins-official marketplaceanthropics/claude-plugins-official | Plugin | 46k | yesterday | Apache-2.0 | A | — | Claude Code |
| nextjsvercel/next.js | Plugin | 143k | yesterday | MIT | A | — | Claude Code |