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/seokan-jeong/team-shinchanWrote 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/seokan-jeong/team-shinchan/team-shinchan)<a href="https://agentmods.dev/plugins/seokan-jeong/team-shinchan/team-shinchan"><img src="https://agentmods.dev/badge/plugins/seokan-jeong/team-shinchan/team-shinchan/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/seokan-jeong/team-shinchan/team-shinchan"><img src="https://agentmods.dev/badge/plugins/seokan-jeong/team-shinchan/team-shinchan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
team-shinchan 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 11d 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": "team-shinchan",
"description": "The Agent Harness for Claude Code — Guardrails, Observability, and Quality Gates for AI-Powered Development. 15 specialist agents with structured workflows, budget controls, analytics, and self-learning.",
"version": "4.58.0",
"author": {
"name": "seokan",
"url": "https://github.com/seokan-jeong"
},
"homepage": "https://github.com/seokan-jeong/team-shinchan",
"repository": "https://github.com/seokan-jeong/team-shinchan",
"license": "MIT",
"keywords": [
"claude-code",
"plugin",
"agent-harness",
"guardrails",
"observability",
"quality-gates",
"multi-agent",
"orchestration",
"self-learning",
"memory",
"analytics",
"budget-guard",
"eval",
"shinchan",
"workflow",
"automation",
"debate",
"code-review",
"planning",
"productivity",
"ai-agents",
"team"
],
"settings": {
"workflow_expiry_days": 7,
"dashboard_autostart": true
}
}
What it installs
The manifest is a name and a version. 40 commands, 15 agents, 1 MCP server travel with it, and installing the plugin installs all of them — 1,015 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command resume A 9 tokens
- Command release A 25 tokens
- Command orchestrate A 14 tokens
- Command fierce-option-panel A 25 tokens
- Command fierce-compete A 15 tokens
- Command fierce-ralph A 19 tokens
- Command fierce-review A 16 tokens
- Command fierce-debate A 15 tokens
- Command bigproject A 12 tokens
- Command design-review A 25 tokens
- Command help A 8 tokens
- Command micro-execute A 16 tokens
- Command review A 16 tokens
- Command debate A 7 tokens
- Command frontend A 15 tokens
- Command manage-skills A 10 tokens
- Command ralph A 8 tokens
- Command analytics A 8 tokens
- Command backend A 14 tokens
- Command devops A 15 tokens
- Command implement A 13 tokens
- Command requirements A 17 tokens
- Command research A 11 tokens
- Command budget A 6 tokens
- Command eval A 7 tokens
- Command session-summary A 7 tokens
- Command setup A 12 tokens
- Command analyze A 8 tokens
- Command autopilot A 8 tokens
- Command deepsearch A 10 tokens
- Command doctor A 5 tokens
- Command lint-harness A 11 tokens
- Command plan A 10 tokens
- Command memories A 5 tokens
- Command brainstorm A 14 tokens
- Command forget A 3 tokens
- Command learn A 5 tokens
- Command impact-analysis A 15 tokens
- Command ontology A 12 tokens
- Command setup-hud B 14 tokens
- Agent misae A 26 tokens
- Agent shinnosuke A 27 tokens
- Agent actionkamen A 26 tokens
- Agent nene A 29 tokens
- Agent bo A 49 tokens
- Agent midori A 67 tokens
- Agent hiroshi A 27 tokens
- Agent aichan A 27 tokens
- Agent masumi A 25 tokens
- Agent himawari A 43 tokens
- Agent kazama A 27 tokens
- Agent masao A 26 tokens
- Agent ume A 72 tokens
- Agent shiro A 30 tokens
- Agent buriburi B 29 tokens
- MCP server shadcn A not measured
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.
- 11d ago First seen · 41 lines scan A 741ea97b78a6
team-shinchan is a plugin published in the GitHub repository seokan-jeong/team-shinchan (8 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-31.
Other plugins, from other repositories
grok
Local Grok CLI delegation: task, review, resumable history, background jobs, stats, and setup health checks.
codex
First party local Codex CLI delegation for tasks, reviews, resumable threads, and durable background jobs.
fusion
Multi-model orchestration: tier agents, routing rules, blind panel, ultra fleet, model config, and drift doctor.
swarm-pi-code-plugin
Portable Pi workflows with durable Host Assistance, discovery, review, and isolated implementation.
relay
Delegate work packets from a lead Claude Code session to executor sessions in their own iTerm tabs, with session reuse instead of always spawning fresh.
orchestra
Conduct a parallel multi-session sprint: one conductor, several work managers in git worktrees, a file-based mailbox, watchdog supervision, and a clean teardown.