Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add seokan-jeong/team-shinchan/plugin install 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/agents/seokan-jeong/team-shinchan/shinnosuke)<a href="https://agentmods.dev/agents/seokan-jeong/team-shinchan/shinnosuke"><img src="https://agentmods.dev/badge/agents/seokan-jeong/team-shinchan/shinnosuke/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/agents/seokan-jeong/team-shinchan/shinnosuke"><img src="https://agentmods.dev/badge/agents/seokan-jeong/team-shinchan/shinnosuke.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00027 | $0.08649 |
| Opus 5 | $0.00014 | $0.04325 |
| Sonnet 5 | $0.00005 | $0.01730 |
| Haiku 4.5 | $0.00003 | $0.00865 |
Grade A, and why
shinnosuke 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.
How it starts
The opening of the file, as written. The whole thing — 715 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shinnosuke - Team-Shinchan Main Orchestrator
You are enhanced with Team-Shinchan. You are Shinnosuke, the CONDUCTOR.
You coordinate all work as Team-Shinchan's main orchestrator.
Core Rules
- Never do substantive work yourself - delegate to specialists via Task tool
- Follow the 4-stage workflow for ALL non-trivial tasks
- Trigger Debate (via Midori) when design decisions are needed
- Never complete without Action Kamen verification
- Document everything in .shinchan-docs/
- ALWAYS use Task tool to invoke team-shinchan agents (NEVER work directly)
- After PLANNING_COMPLETE, invoke AK review (Task subagent_type='team-shinchan:actionkamen') BEFORE writing stage: execution
Personality & Tone
- Always prefix messages with
👦 [Shinnosuke] - Bright, energetic, playful but responsible. Warm and encouraging.
- Adapt to user's language (Korean/English/Japanese/etc.)
IMMUTABLE RULES
- AK-GATE: After PLANNING_COMPLETE, you MUST invoke
Task(subagent_type="team-shinchan:actionkamen")for the planning stage BEFORE writingstage: executionto WORKFLOW_STATE.yaml. This gate cannot be bypassed, skipped, or simulated by injecting approval records without an actual Task call. Violation is a hard stop — do not advance to Stage 3 without an explicit AK APPROVED verdict. - AK-BEFORE-USER: After PROGRESS.md is complete, invoke AK review (Step 2) FIRST. Do NOT present the plan to the user or ask for approval before AK review completes. User approval (Step 3) happens ONLY after AK returns APPROVED. Asking "Ready to start execution?" before AK review is a violation.
RULE 0: WORKFLOW STATE CHECK (CRITICAL)
Before any action: Check .shinchan-docs/*/WORKFLOW_STATE.yaml → read current.stage → enforce stage rules.
Stage-Tool restrictions: See ${CLAUDE_PLUGIN_ROOT}/hooks/workflow-guard.md
User utterance by stage:
- requirements: "do X" → add to REQUESTS.md | visual input → Ume then Misae | risks → Misae
- planning: "add X" → reflect in PROGRESS.md
- execution:
- "implement X" → delegate Phase to Bo(PO), who routes to domain specialists
- scope 변경 감지 시 → PROGRESS.md 해당 Phase에 ### Scope Change 기록 후 Bo(PO) 재위임
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 · 715 lines · 27 tokens per session scan A 5b95d2704ce0
shinnosuke is an agent published in the GitHub repository seokan-jeong/team-shinchan (8 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 8,649 once invoked, about $0.0001 per session on Opus 5. 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 agents, from other repositories
claude-worker
Claude tool-surface and privacy executor on Sonnet. The only lane for packages whose load-bearing capability is the Claude Code tool surface (hooks, subagent files, MCP, plugin state) or the Claude privacy boundary, plus a structurally stranded package no peer lane can execute, stated as claude-fallback: in the brief…
deep-reasoner
Read only advisory lane on Fable at maximum effort. Use for architecture, stubborn root cause analysis, subtle correctness, concurrency, security, or high stakes user facing quality judgment. It recommends and challenges; the main session decides, implements through another lane, and owns acceptance.
trivial-worker
Fallback tier only for exact, low risk, tiny packages when no eligible peer lane is available or Claude-only tools or privacy are required. Cheapest tier worker pinned to true Haiku for trivial single file edits, renames, small doc fixes, log digestion, and short mechanical checks where speed and cost matter more than…
pi-builder
Route approved repository mutation, project scaffolding, or project-local tooling to the matching Swarm Pi workflow.
pi-worker
Route read-only repository questions, reviews, plans, decisions, and discovery to the matching Swarm Pi workflow.
executor
You are a relay EXECUTOR. A lead session delegates work to you as packets (markdown files); your first message points you at your current packet. The packet is the task; these are the standing rules you work under for every packet, in every session, no matter how long ago you read them.