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 s0912758806p/agentic-sop-to-worknpx agentmods add plugins/s0912758806p/agentic-sop-to-work/plugin-forgegit clone --depth 1 https://github.com/s0912758806p/agentic-sop-to-workGrade A, and why
plugin-forge 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": "plugin-forge",
"description": "Claude Code plugin linter + scaffolder. `lint` validates a plugin (or a whole marketplace) against a house grammar — a strict superset of the usual manifest/frontmatter checks plus stdlib-only, hook-protocol, and test-harness invariants; `scaffold` generates a grammar-conformant plugin skeleton that passes the linter by construction. Pure stdlib; self-hosting; runs standalone on any plugin or snaps onto this marketplace.",
"version": "0.1.0",
"author": { "name": "s0912758806p", "url": "https://github.com/s0912758806p" },
"homepage": "https://github.com/s0912758806p/agentic-sop-to-work",
"repository": "https://github.com/s0912758806p/agentic-sop-to-work",
"license": "MIT",
"keywords": ["plugin", "linter", "scaffold", "marketplace", "claude-code", "stdlib", "manifest-validation", "developer-tools", "agentic-sop"]
}
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 · 11 lines scan A cba843b1d680
plugin-forge is a plugin published in the GitHub repository s0912758806p/agentic-sop-to-work (206 stars, last pushed 2mo 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
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.
team
Orchestrates specialized agents to autonomously implement entire features end-to-end.
hyper-waterfall
Claude Code discovery layer for the Hyper-Waterfall framework.
elliot marketplace
Turn any API or database into agent-ready MCP tools. The Elliot marketplace ships the platform plugin (10 skills + MCP server + connector templates).
elliot
Turn any API or database into agent-ready MCP tools. Design, validate, deploy, and observe connector tool sets with Claude.
superscalar
Execution-scheduling discipline for parallel sub-agent dispatch. v0.5.0 / Superscalar v0.14.0 adds the /speculation toggle (§4 speculation authorization) — four modes plus a read-back (off default / auto asks per speculation with the four-element trade-off / on pre-authorizes low-downstream-sensitivity lanes while…