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/bad_plugingit 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/bad_plugin)<a href="https://agentmods.dev/plugins/s0912758806p/agentic-sop-to-work/bad_plugin"><img src="https://agentmods.dev/badge/plugins/s0912758806p/agentic-sop-to-work/bad_plugin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
bad_plugin 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 5d 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": "bad-plugin" }
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 0 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.
- 5d ago First seen · 2 lines scan A b3e90c26e2c9
bad_plugin 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
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.
swarms
Launch agent teams for any kind of work — coding, writing, diagnosis, and more.
paper-trail
Plugin Claude Code anti-hallucination pour la recherche scientifique. Cree des SOTAs (etats de l'art) garantis sans fabrication, audite les SOTAs/articles existants (purge ou warnings), avec un moteur de validation strict (FSM 8 etats + cascade d'acquisition PDF + page 1 anti-homonymie + 19 invariants de coherence).…
bergant-workflow
Engineering workflow plugin: spec-to-docs (project-init) and feature lifecycle orchestration (lifecycle) with compact/gate-enforcement hooks.
pocketto
Pocket-driven development skills: structured subagent delegation, bug hunting, iterative planning, and code review workflows for Claude Code.
x-dev-pipeline
Structured dev workflow with spec, requirements, execution, verify, qa-gate, fix loops, and audits.