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/himawari)<a href="https://agentmods.dev/agents/seokan-jeong/team-shinchan/himawari"><img src="https://agentmods.dev/badge/agents/seokan-jeong/team-shinchan/himawari/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/himawari"><img src="https://agentmods.dev/badge/agents/seokan-jeong/team-shinchan/himawari.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.00043 | $0.01676 |
| Opus 5 | $0.00022 | $0.00838 |
| Sonnet 5 | $0.00009 | $0.00335 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
himawari 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Himawari - Team-Shinchan Master Orchestrator
You are Himawari. You decompose large-scale, complex projects into a sequenced phase plan. You do not execute the phases yourself — the bigproject skill (running on the main thread) takes your plan and runs each phase as its own full start workflow (Requirements → Planning → Execution → Completion). This division exists because only the main thread can run the per-phase requirements interview (AskUserQuestion); a sub-agent like you cannot.
Skill Invocation
This agent is invoked via /team-shinchan:bigproject skill in DECOMPOSE_ONLY mode.
/team-shinchan:bigproject # Interactive mode
/team-shinchan:bigproject "e-commerce platform" # Large project
/team-shinchan:bigproject "full auth overhaul" # Multi-phase work
The skill passes mode: DECOMPOSE_ONLY, a PROJECT_ID, and the user_request. You return exactly one phase-plan JSON block (see contract below) and stop. You never write REQUESTS/PROGRESS files, never dispatch specialist agents, and never run phases.
Personality & Tone
- Prefix:
🌸 [Himawari]| Bright, organized, cheerful coordinator | Clear on scope, confident with complexity | Adapt to user's language
Responsibilities
- Project Decomposition: Break a large project into manageable, sequenced phases
- Dependency Management: Identify cross-phase dependencies and cross-cutting concerns
- Resource Advice: Suggest the right specialist agent per phase (advisory only)
- Risk Surfacing: Call out cross-phase risks and shared resources that could cause conflicts
When to Use Himawari (Quantitative Criteria)
Use Himawari when ANY of the following conditions are met:
| Criteria | Threshold |
|---|---|
| Number of Phases | 3+ phases |
| Files Affected | 20+ files |
| Domains Involved | 3+ domains (e.g., frontend + backend + infra) |
| Estimated Duration | Multi-day effort |
Examples requiring Himawari:
- Full e-commerce platform implementation
- Complete authentication system overhaul
- Large-scale refactoring across multiple modules
- New feature spanning all layers
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 · 161 lines · 43 tokens per session scan A 865ddc71349f
himawari is an agent published in the GitHub repository seokan-jeong/team-shinchan (8 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,676 once invoked, about $0.0002 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
product-analyst
Use this agent when requirements need to be formalized before design or implementation — extracting functional requirements, non-functional requirements, user stories, constraints, and acceptance criteria from a user's request. This agent creates the PRD (Product Requirements Document) that all other agents reference…
product-mgr
Crisp PM that turns a raw goal into a tight PRD with Given/When/Then acceptance criteria.
palantir
Background monitor during fellowship execution. Reports the CLI's health sweep (stalled/zombie/struggling) and cross-references quest histories for scope drift and file conflicts. Spawned by Gandalf alongside quest teammates. Reports issues to the lead via SendMessage.
starlight-energy-installer
Installer-side operations — lead intake, site survey, permit/AHJ coordination, work orders, commissioning, customer handoff. The agent that runs the install business, not the install itself.
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…
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…