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/s0912758806p/agentic-sop-to-workWrote 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/s0912758806p/agentic-sop-to-work/plugin-forge)<a href="https://agentmods.dev/plugins/s0912758806p/agentic-sop-to-work/plugin-forge"><img src="https://agentmods.dev/badge/plugins/s0912758806p/agentic-sop-to-work/plugin-forge/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/s0912758806p/agentic-sop-to-work/plugin-forge"><img src="https://agentmods.dev/badge/plugins/s0912758806p/agentic-sop-to-work/plugin-forge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 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": "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 it installs
The manifest is a name and a version. 1 skill, 1 command, 2 plugins travel with it, and installing the plugin installs all of them — 108 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 11 lines scan A cba843b1d680
plugin-forge is a plugin published in the GitHub repository s0912758806p/agentic-sop-to-work (211 stars, last pushed 1mo 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
aspark
An agile AI product team for Claude Code — Specify, Plan, Act, Review, Keep. A Product Owner, Designer, Engineering Manager, Reviewer, QA Tester and Release Manager work your feature through a gated delivery loop.
x-dev-pipeline
Structured dev workflow with spec, user-global risk RAG, task breakdown, execution, verify, qa-gate, fix loops, and audits.
ai-first-org-design-kit
Fourteen opinionated skills that guide founders and leaders through designing, deploying, adopting, and evolving organizations where agents handle coordination and execution while humans own specification and judgment. Diagnose coordination overhead, encode organizational identity, write agent-ready specifications…
skill-heaven
Skill Heaven is live. Summon one skill into a session with nothing installed: manual /summon at every rung, a clean-room launcher floor (/skill-zero), converge and explore bands over one relevance-ranked summon (/skill-heaven, /skill-hell), and the crown rung (/skill-ultra), from a Skill Tree or a flat GitHub…
context-ledger
Structured product development methodology with traceable evidence, explicit decisions, and constrained spec generation. Forces auditability through semantic IDs, quality gates, and impact-aware updates.
flow
Skill-driven workflow plugin for GitHub development with excellence-by-default quality gates. Encodes team knowledge as composable skills, enforces safety through hooks, and compounds learning across sessions. Strict TDD, Stranger Test, holdout validation, and evidence-based verification built in. Durable goals…