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/tickets)<a href="https://agentmods.dev/commands/chohra-med/expo_boilerplate/tickets"><img src="https://agentmods.dev/badge/commands/chohra-med/expo_boilerplate/tickets/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/tickets"><img src="https://agentmods.dev/badge/commands/chohra-med/expo_boilerplate/tickets.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.00695 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
tickets 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 12d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: tickets — intake work as specs (MCP or inline plan)
Turn work items into the SDD pipeline's fuel. Two sources, same output: a
specs/NNN-<slug>/folder with aspec.md+tasks.mdthatbuildexecutes. You either pull tickets from a ticket MCP or define a plan inline — either way the AI works the resulting tasks under the harness (verifier + learning loop).
Invocation
spec-harness tickets --mcp <server> [--query "<filter>"] # pull from Linear / GitHub / Jira
spec-harness tickets --plan "<describe the work>" # define inline, no ticket system
Or in Claude Code: /spec-harness tickets.
Source A — a ticket MCP (Linear / GitHub Issues / Jira / …)
MCP-agnostic: works with any connected ticket server exposed via ToolSearch. The orchestrator:
- Discovers the ticket tools (
ToolSearch "linear issues"/"github issues"/"jira"). - Lists open tickets matching the query (assignee = me, label, milestone, sprint).
- For each chosen ticket → converts it to
specs/NNN-<ticket-id>-<slug>/spec.md:- the ticket title/body → the spec's "what" (testable acceptance criteria),
- links back to the ticket URL/ID in the spec header (traceability),
- then runs
plan+tasksso it's build-ready.
- On completion, optionally writes status back to the ticket (comment + close) if the MCP exposes a mutation and the human approved write-back.
No ticket MCP connected? The command says so and falls back to Source B. It never invents a ticketing integration that isn't configured.
Source B — an inline plan (no ticket system)
You describe the work in a sentence or a list. The orchestrator writes:
specs/NNN-<slug>/spec.md— the "what" (testable),specs/NNN-<slug>/plan.md— the "how",specs/NNN-<slug>/tasks.md— atomic, ordered, testable units the AI will work through.
This is the "define them into a plan that the AI works on" path.
Then: build
spec-harness build # implement → test → VERIFY → review, one task at a time
Each ticket flows through the full harness. The verifier gates each; learn harvests the
lessons. A ticket isn't "done" until the verifier returns PASS against its acceptance criteria.
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.
- 12d ago First seen · 50 lines · 0 tokens per session scan A f4c8ee788625
tickets is a command published in the GitHub repository chohra-med/expo_boilerplate (34 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 695 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-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…
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'…