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 pinchen147/system-design-skillnpx agentmods add plugins/pinchen147/system-design-skill/system-design-skillgit clone --depth 1 https://github.com/pinchen147/system-design-skillGrade A, and why
system-design-skill 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": "system-design-skill",
"version": "1.1.1",
"description": "Reads a repository as its current architecture, closes the open requirements, runs the capacity math, and compares structurally distinct candidates before recommending one. Outputs an interactive HTML report, a structured design.json, and a durable DESIGN.md.",
"author": {
"name": "Pin Chen",
"url": "https://github.com/pinchen147"
},
"homepage": "https://github.com/pinchen147/system-design-skill",
"repository": "https://github.com/pinchen147/system-design-skill",
"license": "MIT",
"keywords": [
"system-design",
"software-architecture",
"distributed-systems",
"agent-skills",
"capacity-planning"
],
"skills": ["./skills/system-design"]
}
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 21 lines scan A 2f9ed4c1bae5
system-design-skill is a plugin published in the GitHub repository pinchen147/system-design-skill (22 stars, last pushed 21d 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
ainb-hooks
Emit every safely observable Claude Code lifecycle event into Hangar's durable provider log. User-facing events still reach ainb-notifyd over its Unix socket. The same notify.sh powers ATC structured control when installed with AINBMANAGED=atc. stallguard.py additionally blocks turn-end when a session would idle on i.
tdmcp marketplace
Plugin marketplace listing 1 plugin: tdmcp.
uizze
Build product-specific UI with the free anti-ui-slop skill and optional focused UIZZE references.
taskmaster marketplace
Plugin marketplace listing 1 plugin: taskmaster.
harness-maker
Per-project AI coding harness for Claude Code · Cursor · Codex. Profiler + 10-dim interview build a different harness for every project.
skillet
Summon anyone's public skills by handle, or route a task to the best skill in your own kit.