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/commands/seokan-jeong/team-shinchan/resume)<a href="https://agentmods.dev/commands/seokan-jeong/team-shinchan/resume"><img src="https://agentmods.dev/badge/commands/seokan-jeong/team-shinchan/resume/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/commands/seokan-jeong/team-shinchan/resume"><img src="https://agentmods.dev/badge/commands/seokan-jeong/team-shinchan/resume.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.00009 | $0.01608 |
| Opus 5.5 | $0.00004 | $0.00643 |
| Sonnet 5.5 | $0.00002 | $0.00322 |
| Haiku 4.5 | $0.00001 | $0.00161 |
Grade A, and why
resume 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Workflow Command
EXECUTE IMMEDIATELY
When this command is invoked, DO NOT explain the process. EXECUTE the resume workflow.
Usage
/team-shinchan:resume # Auto-detect interrupted workflows
/team-shinchan:resume main-016 # Resume specific workflow by DOC_ID
/team-shinchan:resume ISSUE-123 # Resume workflow by Issue ID
Execution Protocol
1. Input Validation
If no DOC_ID provided:
- Scan
.shinchan-docs/*/WORKFLOW_STATE.yaml(skiparchived/subfolder) — filterstatus: active|paused - Scan
.shinchan-docs/archived/*/*/WORKFLOW_STATE.yaml— collect all entries - Display:
Active/Paused: 1. {DOC_ID} ({status}, {stage}) Archived: A1. {DOC_ID} (expired, {stage}, archived {YYYY-MM}) - If user selects archived entry: unarchive first (move to
.shinchan-docs/{DOC_ID}/, set status: paused, add unarchived event), then proceed - If both empty: "No interrupted workflows found."
If DOC_ID provided:
- Check
.shinchan-docs/{DOC_ID}/first, then.shinchan-docs/archived/*/{DOC_ID}/ - If found in archived: unarchive before proceeding
- Error if not found anywhere: List available workflows
2. Load State
Read .shinchan-docs/{DOC_ID}/WORKFLOW_STATE.yaml:
- Extract:
current.stage,current.phase,current.owner - Verify:
status != completed
3. Load Context
Required:
REQUESTS.md- Problem statement, requirements, AC
Conditional:
PROGRESS.md- If stage is planning/execution/completion
4. Update State
Append to WORKFLOW_STATE.yaml history:
- timestamp: "{ISO 8601}"
event: resumed
agent: shinnosuke
from_stage: {stage}
from_phase: {phase}
Set current.status: active
5. Announce Resume
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
▶️ Workflow Resumed: {DOC_ID}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📋 Stage: {stage} ({N} of 4)
🔄 Phase: {phase}
👤 Owner: {owner}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6. Delegate to Agent
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 · 268 lines · 9 tokens per session scan A f13653d2b68e
resume is a command published in the GitHub repository seokan-jeong/team-shinchan (9 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 1,608 once invoked, about $0.0000 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 commands, from other repositories
setup
Scaffolds the project and sets up the Conductor environment for spec-driven development.
cto-advisor
Run CTO-level technical review of the current execution plan - architecture, tech debt, engineering excellence.
board-meeting
Full board deliberation with discussion rounds - directors debate and reach consensus.
close-track
Close a completed track — run quality gate, update conductor state, commit, and optionally handle the git branch.
go
The single entry point to the Conductor system - state your goal and everything is handled automatically.
ui-audit
Run comprehensive UI/UX design validation against design principles, accessibility standards, and usability laws.