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 sgaunet/claude-pluginsnpx agentmods add plugins/sgaunet/claude-plugins/software-engineeringgit clone --depth 1 https://github.com/sgaunet/claude-pluginsGrade A, and why
software-engineering 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 2d 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": "software-engineering",
"version": "0.21.0",
"description": "Code review, debugging, documentation, license compliance (AGPL/MIT/Apache), payment integration (Stripe/PayPal), frontend development (HTMX/Alpine.js), architecture diagrams (d2 via diagram-architect + /gen-diagram), and terminal demo GIFs (VHS via /gen-vhs-demo). Skills: auto-mr (push/MR/merge), detect-repo-host (platform routing), run-lint, run-tests. MCP: context7",
"keywords": [
"code-review",
"security",
"documentation",
"payments",
"git",
"diagrams",
"d2",
"architecture-diagrams",
"vhs",
"demo-gif"
],
"author": {
"name": "Sylvain",
"email": "[email protected]"
},
"license": "MIT",
"repository": "https://github.com/sgaunet/claude-plugins",
"homepage": "https://github.com/sgaunet/claude-plugins#readme"
}
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.
- 2d ago First seen · 25 lines scan A 4c344692a14b
software-engineering is a plugin published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 7d 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
pm-skills
Structured AI workflows for better product decisions. 68 domain-specific skills and 42 chained workflows across 9 PM plugins — from discovery to strategy, execution, launch, growth, and shipping AI-built software.
pm-ai-shipping
AI Shipping Kit — for PMs and founders accountable for AI-built code. Document a vibe-coded app, audit it for intended-vs-implemented security gaps and performance issues, and produce a reviewer-ready shipping packet.
pm-execution
Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.
pm-go-to-market
Go-to-market skills for PMs: GTM strategy, growth loops, GTM motions, beachhead segments, and ideal customer profiles.
cc-handbook
Plugin marketplace listing 19 plugins: handbook, handbook-extras, handbook-qa, handbook-dotnet, handbook-microsoft-docs.
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.