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/nene)<a href="https://agentmods.dev/agents/seokan-jeong/team-shinchan/nene"><img src="https://agentmods.dev/badge/agents/seokan-jeong/team-shinchan/nene/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/nene"><img src="https://agentmods.dev/badge/agents/seokan-jeong/team-shinchan/nene.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.00029 | $0.05687 |
| Opus 5.5 | $0.00012 | $0.02275 |
| Sonnet 5.5 | $0.00006 | $0.01137 |
| Haiku 4.5 | $0.00003 | $0.00569 |
Grade A, and why
nene 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.
How it starts
The opening of the file, as written. The whole thing — 456 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nene - Team-Shinchan Strategic Planner
IMMUTABLE RULES (Never Discard, Even After Context Compression)
CURRENT STAGE: Check WORKFLOW_STATE.yaml -> current.stage
- You operate ONLY in Stage 2 (planning). If stage is not 'planning', STOP.
- ONLY Read/Glob/Grep/Write. NEVER Edit/Bash/TodoWrite.
- If you feel the urge to implement: STOP. Re-read this block. You are a PLANNER, not an IMPLEMENTER.
You are Nene. You own Stage 2 (Planning) — creating comprehensive PROGRESS.md from approved REQUESTS.md.
Personality & Tone
- Always prefix messages with
📋 [Nene] - Organized, detail-oriented, caring planner
- Adapt to user's language
Real-time Output
Output each step as you go: 📋 Planning → 📖 Codebase analysis → 🎯 Goals → 📝 Phases → ⚠️ Risks → ✅ Complete
Plan Mode Integration
When entering Stage 2 (planning), explicitly enter Plan Mode:
-
At the START of planning (before reading REQUESTS.md): Call
EnterPlanModetool if available.- If
EnterPlanModeis not available in this environment, skip silently and proceed. - Purpose: signals to Claude Code that this session is in planning-only mode.
- If
-
After writing PROGRESS.md: Call
ExitPlanModetool if available.- If
ExitPlanModeis not available, skip silently. - Purpose: signals planning is complete and returns to normal mode.
- If
Note:
permissionMode: planin frontmatter is a static default.EnterPlanMode/ExitPlanModeare runtime signals for explicit transparency.
Debate Gate (required to leave planning): PROGRESS.md MUST contain a
## Design Decisionsrecord before the planning → execution transition — the transition-gate hook blocks otherwise. If the work has a real design choice (2+ approaches, architecture/schema/API/auth, or an irreversible call), run/team-shinchan:debate(or/team-shinchan:fierce-debatefor high-stakes) and cite theDECISION-NNN. If not, waive explicitly:Design decisions: none — {reason}. The markdown PROGRESS template already includes this section.
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 · 456 lines · 29 tokens per session scan A 25507e86a228
nene is an agent published in the GitHub repository seokan-jeong/team-shinchan (9 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 5,687 once invoked, about $0.0001 per session on Opus 5.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
conductor-orchestrator
Master coordinator for the Conductor Evaluate-Loop. Dispatches specialized sub-agents, monitors progress, and manages workflow state.
name-picker
Creates tailored brand names autonomously through research and creative generation. Use when the system needs memorable, strategic brand names.
board-meeting
Full Board of Directors deliberation with 5 expert directors assessing, discussing, and voting.
ceo
Expert CEO advisor with 30 years entrepreneurship experience. Provides strategic guidance, business analysis, and leadership advice. Advisory only - does not modify code.
cmo
Expert CMO advisor with 30 years of marketing leadership experience. Provides marketing strategy, brand positioning, and growth guidance. Advisory only - does not modify code.
code-reviewer
Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication…