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.
npx agentmods add skills/skullninja/coco-workflow/interviewnpx skills add skullninja/coco-workflow --skill interviewgit clone --depth 1 https://github.com/skullninja/coco-workflowWhat 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 | $0.00032 | $0.01314 |
| Opus 5 | $0.00016 | $0.00657 |
| Sonnet 5 | $0.00006 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
interview 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coco Interview Skill
Conduct a structured pre-design interview to gather deep user intent, constraints, and context before generating a feature design. Produces a discovery brief that feeds directly into the design skill.
When to Use
- Pre-design discovery for Standard-tier features (before invoking the
designskill) - Deep-dive during any planning session (strategic, tactical, operational, triage)
- Natural language requests ("interview me about this feature", "let's discuss requirements")
- When
/coco:phaseor/coco:planning-session tacticalroutes to Standard tier
Do NOT use for:
- Trivial-tier features (use
hotfixskill directly) - Light-tier features (skip interview, use
designin light mode) - Features where the user has already provided exhaustive requirements
Setup
- Read
.coco/config.yamlforproject.specs_dir(default:specs). - Determine the feature from conversation context:
- If a feature name or description was provided, use it
- If on a
feature/*git branch, extract the feature name - If none of the above, ask the user what feature to discuss
- Determine the feature directory:
{specs_dir}/{feature-name}/ - Load the discovery template from
.coco/templates/discovery-template.mdif it exists, otherwise use${CLAUDE_PLUGIN_ROOT}/templates/discovery-template.md. - Check if
{specs_dir}/{feature-name}/discovery.mdalready exists:- If yes, enter refinement mode (see below)
- If no, proceed with fresh interview
Execution
Category Progression
The interview covers these categories in order, adapting based on what the user has already provided:
- Problem & Motivation -- What problem does this solve? Who feels the pain? Why now?
- Users & Personas -- Who are the target users? What are their goals and skill levels?
- Scope & Boundaries -- What's explicitly in scope? What's out of scope? MVP vs future?
- Functional Requirements -- What are the core behaviors? What are the key user flows?
- Technical Context -- What existing systems does this interact with? Any constraints?
- UX & Interaction -- What does the user experience look like? Key screens/flows?
- Non-Functional Requirements -- Performance, security, accessibility, scalability?
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.
- 2d ago First seen · 120 lines · 32 tokens per session scan A d142b2e2a9e0
interview is a skill published in the GitHub repository skullninja/coco-workflow (7 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 1,314 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 skills, from other repositories
council-review
Perform a rigorous Carmack Council code review. Use when explicitly asked to review code, do a "council review", "carmack review", or invoke /council-review. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js)…
council-plan
Architect a feature with the Carmack Council before writing code. Use when explicitly asked to plan a feature, do a "council plan", "carmack plan", or invoke /council-plan. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo…
test-architect
Map testable surfaces, audit existing tests for quality, and write test specifications that prevent AI shortcuts. Use when asked to "audit tests", "specify tests", "test architect", "map test coverage", or invoke /test-architect. Two modes — audit (evaluate existing tests against Beck's principles) and specify (write…
spec-writer
Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this…
council-implement
Execute a Carmack Council plan task by task. Use when explicitly asked to implement a plan, do a "council implement", "carmack implement", "council build", or invoke /council-implement. Reads the output of /council-plan and builds each task sequentially, loading the relevant expert's reference document per task.…
project-butler
Project memory workflow for init/upgrade, profile-aware setup, end session, normal/full close, file organization, document archiving, language switching, versioned update logs, rule review, status, wiki sync, and context recovery. Use for /project-butler, setup/初始化, foundation setup, profile setup, end session/收工…