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/chohra-med/expo_boilerplateWrote 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/chohra-med/expo_boilerplate/init)<a href="https://agentmods.dev/commands/chohra-med/expo_boilerplate/init"><img src="https://agentmods.dev/badge/commands/chohra-med/expo_boilerplate/init/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/chohra-med/expo_boilerplate/init"><img src="https://agentmods.dev/badge/commands/chohra-med/expo_boilerplate/init.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.00000 | $0.01206 |
| Opus 5 | $0.00000 | $0.00603 |
| Sonnet 5 | $0.00000 | $0.00241 |
| Haiku 4.5 | $0.00000 | $0.00121 |
Grade A, and why
init 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 9d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: init — spec-driven bootstrap
Stand up the whole system in a target project from a goal, not from a blank template. This is the "init function where we explain what we want to achieve": you hand it intent, it produces the memory bank + rules + agents + the first spec.
Invocation
spec-harness install <path> new <name> # greenfield: scaffold from a goal
spec-harness install <path> integrate <name> # existing repo: add without clobbering
spec-harness init <path> <name> # greenfield only (full interview)
Or, in Claude Code: /spec-harness:init and answer the interview. install is the one entry
point for both "start a new project with it" and "integrate it into an existing one" — it
auto-detects the mode (.git/package.json/pyproject ⇒ integrate) and is idempotent.
Step 1 — capture intent (the interview, one message)
Ask all of these up front; pre-fill any the brief/repo already answers, then confirm:
- Mode — new (greenfield) or integrate (existing repo)? (auto-detected; confirm.)
- Project name + one-sentence purpose.
- Stack — language, framework, datastore, test runner, lint/format, typecheck command.
- Hard constraints — perf, privacy, regulatory, "graders punish over-engineering", deadline.
- Existing entry point? (
CLAUDE.md/AGENTS.md/.cursorrules— merge, never overwrite.) - Work intake — where do tasks come from? A ticket MCP (Linear/GitHub/Jira — which?) or
inline plans? (Configures the
ticketscommand's default source.) - Learning goals — what should the human operator be levelling up on while this ships
(e.g. "RN performance", "LangGraph", "SDD")? Seeds
learning/NOTES.mdso the loop's TEACH step targets real goals, not noise. - Regression guards — any code that must NOT be touched (auth overrides, hardened paths)?
Captured into
AGENTS.mdas ratchet rules on day one.
If a brief/spec file is supplied (e.g. a decoded take-home), read it and pre-fill — don't
re-ask what the brief or the repo already answers. Integrate mode: also run index first so
the answers are grounded in the real code.
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.
- 9d ago First seen · 78 lines · 0 tokens per session scan A 00ed75a83ef3
init is a command published in the GitHub repository chohra-med/expo_boilerplate (32 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,206 tokens. 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-30.
Other commands, from other repositories
arc-skill
You are scaffolding a new React Native (Expo) project using the arc-skill architecture.
arc-connect
Connect API layer, storage, state management, authentication, and i18n to an existing React Native Expo project. Use after arc-scaffold to add backend integration. Trigger when the user mentions adding API calls, auth flow, login, storage, state management, internationalization, backend connection, or data fetching to…
arc-ui
Add theme system, reusable components, screen layouts, and mobile UX design to a React Native Expo project. Use after arc-scaffold to build the visual layer. Trigger when the user wants to add a theme, dark mode, UI components, buttons, inputs, screen layouts, design system, or visual polish to their React Native app.
arc-audit
Audit a React Native Expo project for mobile UX issues, performance problems, and architecture violations. Use to check code quality against arc-skill best practices. Trigger when the user asks to review code, check for issues, wants a health check, mentions touch targets, accessibility, performance audit, or says 'is…
arc-feature
Add a complete new feature domain to an existing React Native Expo project — types, API module, React Query hooks, screen, and components in one go. Use when adding a new entity like products, orders, chat, users, recipes, or any CRUD resource. Trigger when the user says 'add a feature', 'create a new screen for X'…
arc-scaffold
Scaffold a new React Native Expo project with folder structure, dependencies, TypeScript config, linting, and navigation shell. Use when starting a new mobile app from scratch, when the user says 'create a new app', 'start a project', 'set up React Native', 'init Expo app', or needs project boilerplate. Trigger this…