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-teamgit 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.00013 | $0.00906 |
| Opus 5 | $0.00006 | $0.00453 |
| Sonnet 5 | $0.00003 | $0.00181 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
app-team 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.
What it actually says
/app-team — Roster
Print the team in this order, each line as <role> — <one-line charter>:
Exec
- ceo — vision, success metrics, scope
- cpo — PRD, user stories, backlog
- cto — architecture, stack, engineering principles (starts from the House KB defaults)
- chief-of-staff — the single founder interface: decision briefs, unresolved commitments, founder inbox (flagship, and only when it removes more decisions than it creates)
Product
-
product-manager — day-to-day product execution below the CPO: ticket clarification, backlog grooming, in-sprint scope calls
-
product-researcher — independent evidence gathering, with fact / user evidence / competitor observation / hypothesis / agent inference labelled separately (conditional)
-
product-validator — compares the founder's recorded brief to the PRD and flags omitted intent, invented requirements and silent scope change. Sits outside the cpo/cto/tech-manager chain, reports to the scope-lock gate, and never writes the PRD it checks
Management
- tech-lead — per-platform impl specs, patterns, hands-on senior
- tech-manager — sprint plan, board, daily report, merge gate, standups, pod coordination
Build
- ios-developer — Swift/SwiftUI implementation, routes through Axiom skills (multiple in parallel)
- android-developer — Kotlin/Compose implementation, Material 3 skills (multiple in parallel)
- web-developer — TypeScript/browser implementation; the IC that makes
web-appa staffed product type - backend-developer — API + persistence (if backend in scope); activates as the
ai-engineer,data-engineerorintegration-engineervariant when the architecture calls for one - monetization-engineer — StoreKit/Play Billing IAP, paywall gateway, AdMob + consent
- code-reviewer — gate on every PR-equivalent; runs Axiom auditors on iOS branches
- qa-engineer — test plans, bug filing, ship sign-off
- test-automation-engineer — test infrastructure, the device and state matrix, evidence bundles, flake detection (flagship, conditional)
- verification-engineer — executes what everyone else asserts: sweeps constants against outside reference data, grades every guard rule, and must watch a rule fail before trusting it
Design & Growth
- ux-architect — information architecture, navigation, flows, the screen-and-state inventory
- product-designer — screen composition, hierarchy, interaction, visual quality, tokens, components
- aso-specialist — store listing, keywords, screenshots, store-readiness gate
- data-analyst — analytics schema, instrumentation check, post-launch KPI report
Platform & Release
- devops-engineer — git strategy, CI, signing, flavors, secrets hygiene
- security-reviewer — pre-ship MASVS pass, severity-classified findings (and the privacy checklist as its privacy mode on utility projects)
- privacy-reviewer — data inventory, consent, retention, regional compliance (flagship)
- reliability-engineer — offline, retries, idempotency, sync conflict, state restoration, recovery (flagship, conditional)
- red-team-agent — attacks the product and the studio's own assumptions (flagship, conditional)
- release-manager — version, signing, store upload, release notes
- release-auditor — independently reviews the evidence bundle and the gate record, and can block the
release.
release-managercannot satisfy it — separation of duties - incident-commander — owns coordination, containment, and resolution for an open sev1/sev2 incident (conditional, activates only while one is open)
End by reminding the user that not every role runs on every project: role-activation decides
the roster from the product type and tier, records every deactivation with its reason in
docs/02-team-roster.md, and refuses outright on a product type no IC can build. Also that team
size can be tuned per project via the tech-manager agent, and that all build agents read the
Mobify Studio House Knowledge Base (knowledge/) before working.
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 · 70 lines · 13 tokens per session scan A 43094cbbb784
app-team is a command published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It adds 13 tokens to every session and 906 once invoked, about $0.0001 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
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
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.
doctor
Diagnose installation health. Check Node, CDP bridge, rn-fast-runner (iOS), rn-android-runner (Android), maestro-runner, simulators, Metro, CDP, injected helpers, ffmpeg, physical devices, plugin version, Vercel rules sync. Reports what's missing — does NOT modify your project.
compose-preview
Generate and verify Compose previews for UI components.
android-build
Build Android project with Gradle, fix errors, generate APK/AAB. Invokes android-build-resolver for issues.