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/marcusrbrown/systematicWrote 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/marcusrbrown/systematic/marketplace)<a href="https://agentmods.dev/plugins/marcusrbrown/systematic/marketplace"><img src="https://agentmods.dev/badge/plugins/marcusrbrown/systematic/marketplace/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/marcusrbrown/systematic/marketplace"><img src="https://agentmods.dev/badge/plugins/marcusrbrown/systematic/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
systematic marketplace 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 2mo 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": "systematic",
"owner": {
"name": "Marcus R. Brown",
"email": "[email protected]"
},
"plugins": [
{
"name": "systematic",
"description": "Compound-engineering loops for OpenCode, Pi, and Claude Code",
"source": {
"source": "github",
"repo": "marcusrbrown/systematic",
"ref": "claude-code-plugin"
}
}
]
}
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.
- 2mo ago First seen · 19 lines scan A 6c9f4107a830
systematic marketplace is a plugin published in the GitHub repository marcusrbrown/systematic (28 stars, last pushed today), 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.
systematic marketplace compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| systematic marketplacemarcusrbrown/systematic | Plugin | 28 | today | MIT | A | — | Claude Code |
| no-viberizukirr/no-vibe | Plugin | 46 | 6d ago | MIT | A | — | Claude Code |
| dodopaymentsdodopayments/dodo-agent-plugin | Plugin | 7 | 7d ago | MIT | A | — | Claude Code |
| dodopaymentsdodopayments/dodo-agent-plugin | Plugin | 7 | 7d ago | MIT | A | — | Gemini CLI |
| open-magiladiossoop5star/open_magi | Plugin | 3 | 1mo ago | MIT | A | — | Claude Code |
| session-hooks-templatejohnlindquist/claude-session-hooks-template | Plugin | 5 | 10mo ago | MIT | A | — | Claude Code |
| merismosjongwony/epistemic-protocols | Plugin | 175 | today | MIT | A | — | Claude Code |