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 commands/vmobifystudio/app-dev-team/app-rungit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWhat 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.00035 | $0.02978 |
| Opus 5 | $0.00017 | $0.01489 |
| Sonnet 5 | $0.00007 | $0.00596 |
| Haiku 4.5 | $0.00003 | $0.00298 |
Grade A, and why
app-run 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 yesterday.
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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-run — Drive the whole build, mostly on its own
Idea / flags: $ARGUMENTS
This is the autonomous driver. It chains init → plan → build → standup → loop until the sprint is
done or a true blocker hits. Only two things stop for the user: scope-lock and ship. Everything
else streams as standup reports. Wrap this command in /loop for fully self-paced execution.
Operating rules
- The team never invents intent. When a requirement is genuinely ambiguous, write the blocker to the standup and surface it verbatim — do not guess.
- All build agents invoke the
house-conventionsskill before working (House KB =knowledge/). - Honor the existing safety rails: 2-cycle review cap, no auto-merge across
REQUEST CHANGES, one agent per ticket at a time, no destructive data actions. - The board doctor gate is not skippable, including under
--yolo.--yoloskips human gates, never correctness gates. An autonomous run is exactly the situation where a silently stranded ticket goes unnoticed for the whole sprint. - No
DONEis believed unverified.verify-done.shruns on every developer return —--staticby default, which checks the branch, the commits and the changed files and states plainly that the suite has not run. The suite runs once per wave on the merged tree (step 4). "Verified" here never means "an agent said so".
Steps
-
Detect greenfield vs brownfield. Using the
brownfield-onboardingskill's detection, check whether the target directory already contains an app.Either branch writes
docs/02-team-roster.mdvia therole-activationskill before it spawns anyone.--utilitysets the tier; without it the tier is derived and stated at Gate 1, where scope is approved anyway. Everything after this step spawns from the roster and never from a list in this file — read it, do not re-derive it.offroles are not spawned; their gates reportN/Awith the roster's reason, never silence.- Empty / no app → greenfield: run
/app-initwith the idea (requirements-intake → CEO vision → parallel CPO/CTO → parallel ux-architect/product-designer/tech-lead/devops-engineer → project bootstrap incl.CLAUDE.md+ git)./app-initends with its own scope-lock gate — this command owns that gate (step 2), so/app-initskips it here and the user is asked once, not twice. - Existing app → brownfield: run
/app-onboard(reverse-engineer the as-built baseline +CLAUDE.md), then/app-audit(grade vs the House KB →docs/80-audit.md→ remediation backlog). If an idea/goal was given, treat it as the upgrade goal and add it as feature tickets alongside theAUDIT-NNNremediation tickets.
- Empty / no app → greenfield: run
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.
- yesterday First seen · 164 lines · 0 tokens per session scan A fddf63a909a2
app-run is a command published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It adds 35 tokens to every session and 2,978 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 commands, from other repositories
factory-report
Linear status report across configured repos — queue depth, triage backlog, ready-to-dispatch, blocked/held.
analyze-cluster-postmortem
Postmortem analysis of cluster failures → OPTIMIZE PROMPTS to work for EVERY use case.
ab
Show Kanban board or list view (shortcut for board).
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
factory-next
Recommend and optionally run the next factory stage for this repo.
sprint-status
Show status across active parallel sessions.