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/shangyankeji/super-devWrote 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/shangyankeji/super-dev/marketplace)<a href="https://agentmods.dev/plugins/shangyankeji/super-dev/marketplace"><img src="https://agentmods.dev/badge/plugins/shangyankeji/super-dev/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/shangyankeji/super-dev/marketplace"><img src="https://agentmods.dev/badge/plugins/shangyankeji/super-dev/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
super-dev 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 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": "super-dev-local",
"plugins": [
{
"name": "super-dev-claude",
"source": "./plugins/super-dev-claude",
"version": "2.3.8"
}
]
}
## Super Dev System Flow Contract
- SUPER_DEV_FLOW_CONTRACT_V1
- PHASE_CHAIN: research>docs>docs_confirm>spec>frontend>preview_confirm>backend>quality>delivery
- DOC_CONFIRM_GATE: required
- PREVIEW_CONFIRM_GATE: required
- HOST_PARITY: required
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 · 18 lines scan A 9879af21e130
super-dev marketplace is a plugin published in the GitHub repository shangyankeji/super-dev (276 stars, last pushed 4mo 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
coco
Autonomous spec-driven development for Claude Code. Describe a feature, get merged, tested, reviewed code.
people-management
AI-augmented management tooling for people managers. Surfaces the right context at the right time: before meetings, during 1:1 prep, when triaging messages, or reviewing customer status. Adapts to your org's performance and management frameworks. Augments managers, never automates.
papi
Persistent project management inside your AI coding tool. PAPI plans what to build next, tracks every decision, and keeps projects coherent across sessions — so a new session starts where the last one left off instead of from nothing.
commander-hub marketplace
Plugin marketplace listing 1 plugin: commander.
codoop-flow
In-session orchestration for the codoop-flow Agent-Centric ticket pipeline: pick -> build -> verify -> review -> ship, driven by a skill plus a deterministic guardrail CLI.
oh-my-pm
A product-management workflow system covering research, strategy, product requirements, prototypes, delivery, launches, and feedback.