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 aminry/auto-claude-pluginsnpx agentmods add plugins/aminry/auto-claude-plugins/auto-developgit clone --depth 1 https://github.com/aminry/auto-claude-pluginsGrade A, and why
auto-develop 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": "auto-develop",
"version": "1.0.0",
"description": "Creates custom auto-develop loops for any feature in any codebase — analyzes features, builds capability specs, and generates autonomous iterative development skills that add new functionality",
"author": {
"name": "Amin Roudaki",
"url": "https://github.com/aminry"
},
"repository": "https://github.com/aminry/auto-claude-plugins",
"license": "MIT",
"keywords": [
"auto-develop",
"capability",
"specification",
"feature-development",
"automation",
"iterative-development"
]
}
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 · 20 lines scan A 4a817041d2df
auto-develop is a plugin published in the GitHub repository aminry/auto-claude-plugins (1 stars, last pushed 3mo 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
claude-ai-music-skills
AI music generation workflow for Suno - album concepts, lyrics, prompts, mastering, release.
bitwize-music
Plugin marketplace listing 1 plugin: bitwize-music.
automating-mac-apps-plugin
Plugin marketplace listing 1 plugin: automating-mac-apps.
automating-mac-apps
Automates macOS apps via Apple Events using AppleScript (discovery) and JXA (production logic). Use when asked about AppleScript, JXA, osascript, or macOS app automation.
moo.md
mind on output — stay present with AI.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.