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/ancoleman/ai-design-componentsWrote 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/ancoleman/ai-design-components/developer-productivity-skills)<a href="https://agentmods.dev/plugins/ancoleman/ai-design-components/developer-productivity-skills"><img src="https://agentmods.dev/badge/plugins/ancoleman/ai-design-components/developer-productivity-skills/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/ancoleman/ai-design-components/developer-productivity-skills"><img src="https://agentmods.dev/badge/plugins/ancoleman/ai-design-components/developer-productivity-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
developer-productivity-skills 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": "developer-productivity-skills",
"description": "API design, CLI development, SDK creation, documentation generation, debugging, and Git workflows",
"source": "./",
"skills": [
"./skills/designing-apis",
"./skills/building-clis",
"./skills/designing-sdks",
"./skills/generating-documentation",
"./skills/debugging-techniques",
"./skills/managing-git-workflows",
"./skills/writing-github-actions"
],
"strict": false
}What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 391 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#developer-productivity-skills 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.
- 1mo ago First seen · 15 lines scan A bf448aabd532
developer-productivity-skills is a plugin published in the GitHub repository ancoleman/ai-design-components (525 stars, last pushed 10mo 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.
Other plugins, from other repositories
distributed-debugging
Distributed system tracing and debugging across microservices.
sre-bot
SRE triage assistant for plain-English production health and Kubernetes questions in Slack. One pinned upstream Kubernetes MCP connector exposes the core toolset: reads execute immediately, six mutations require a fresh human approval, and unmatched tools fail closed. Kubernetes RBAC limits writes to disposable…
docs
Documentation that stays true to the code: architecture decision records with an /adr command, READMEs verified against the repository, developer guides in the four documentation types, and OpenAPI specifications kept in sync in CI.
api-design
Comprehensive API design skill for REST, GraphQL, gRPC, and Python library architectures. Design endpoints, schemas, authentication, pagination, error handling, and federation.
content-modelling
Design content models with types, fields, relationships, and governance rules for structured content systems.
bulkhead-pattern
Generate bulkhead isolation patterns.