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 theafh/ai-modulesnpx agentmods add plugins/theafh/ai-modules/ai_devgit clone --depth 1 https://github.com/theafh/ai-modulesGrade A, and why
ai_dev 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": "ai_dev",
"version": "1.11.15",
"description": "Skills and agents for everyday AI-assisted development: structured git commits, safe repository refresh and branch cleanup, day-grouped changelog maintenance, project-local task and todo tracking as plain-markdown files (a base task skill plus create, check, auto-check, explain, select, implement, audit, finish, and fix siblings with auto_*_task helper agents, including task_auto_check's auto_drift_task intent check and task_fix's auto_shaper_task escalation), repo-root guardrail documents that keep autonomous agents anchored to human intent (a guardrail hub skill plus a guardrail_audit sibling, with per-type templates and rules for CHARTER, ARCHITECTURE, TESTING, and SECURITY docs), writing and formatting AI instructions (prompts, rules, skill files, agent definitions), skill_doctor for check-only audits of skill artifacts, descriptions, registration, and tests, harness portability for bundled scripts and plugin wiring, and language style guides for markdown, Python, and Rust.",
"author": {
"name": "Andreas F. Hoffmann"
},
"license": "MIT"
}
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 · 10 lines scan A 68f76211419a
ai_dev is a plugin published in the GitHub repository theafh/ai-modules (38 stars, last pushed 2d 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-30.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.