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/vmobifystudio/app-dev-team/requirements-intakenpx skills add vmobifystudio/app-dev-team --skill requirements-intakegit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/skills/vmobifystudio/app-dev-team/requirements-intake)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/requirements-intake"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/requirements-intake.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.00769 |
| Opus 5 | $0.00036 | $0.00385 |
| Sonnet 5 | $0.00014 | $0.00154 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
requirements-intake 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 today.
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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements intake
You are converting fuzzy human intent into a structured intake doc. You are not the CEO yet — you are the funnel.
When to use
- User starts a project with a one-liner ("Build a habit tracker", "An app for X")
- The CEO agent needs a clean input
/app-initis called
Procedure
-
Read what the user said. Extract whatever's already there:
- Product idea
- Target user (if named)
- Platform preference (if named)
- Constraints (timeline, budget, must-haves)
-
For everything missing, ask the user in one round with at most 5 questions. Use the AskUserQuestion tool if available. Cluster questions; don't drip them.
The five questions, in priority order:
-
Who is this for? (one specific persona, not a market)
-
What is the single most important thing they'll do in the app?
-
What kind of product is this — iOS app, Android app, both, web app, backend service, CLI tool, or a library? If more than one, which ships first?
This question used to ask "iOS, Android, or both", which could not describe a product that is neither.
role-activationreads its answer to decide which specialists exist at all, and a product type it cannot read from here it has to guess at. -
What does success look like in 6 months? (numbers if possible)
-
Anything that's explicitly out of scope?
-
2a. Record the raw material first. Before you structure anything, put the user's own words —
the original one-liner, your five questions and their answers, and anything they pasted or
linked — into docs/00-founder-intent/ verbatim and dated, then run
node "${CLAUDE_PLUGIN_ROOT}/scripts/founder-intent.mjs" --project-root . --write.
The intake below is already an interpretation: it clusters, it phrases, it drops what did not fit
a heading. That is fine as long as the un-interpreted version still exists to check it against —
product-validator compares the two, and it cannot compare against something nobody kept. The
directory is append-only; a later change of mind is a new dated line in its decisions.md.
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.
- today First seen · 88 lines · 71 tokens per session scan A 79772f8f0d89
requirements-intake is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 71 tokens to every session and 769 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
prd
Generates a Product Requirements Document from a natural language app description. Asks clarifying questions, researches similar apps, defines scope, stack, architecture, and produces a structured PRD that Archon can decompose into a campaign.
execute-task
Implement one task (or a cohesion bundle) from a signed-off spec (Ready or Active): recompute the execution freshness gate, write the verifying test first, implement to green, run the project's full CI with adaptive retry, converge via the configured reviewsequence (default /polish --nested), then open a draft PR…
builder
Detect a project's stack and recommend or apply the universal mechanical quality guards from planwright's core catalog (formatter, linters, type-checker, test runner, secret scan, commit hooks, CI gate), plus the growable breadth dimensions. Escalates stake-bearing decisions (auth, data modeling, security posture…
spec-walkthrough
Render a spec bundle (or a chosen slice) into a plain-language, didactic comprehension artifact a human reads and judges for themselves: an unaided cold read before kickoff, re-orientation mid-execution, or onboarding to a finished or abandoned spec. Standalone and strictly read-only: it renders any status, never…
drain
Run the on-demand drain pass over every spec bundle's Gate deferral entries: evaluate structured GATE(when:) conditions, surface date and free-text gates, report malformed ones, inventory each live bundle's [manual] test-spec entries, and surface the observations log's unmined state. Read-only; nothing is…
orchestrate
Advance one planwright spec by one step: pick the next ready unit critical-path-first (or a cohesion bundle), run the freshness gate, record the dispatch under the per-spec lock, and dispatch /execute-task via the backend. A stateless, disposable control tower; a reconcile sweep rebuilds from disk. Never merges, marks…