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/iampawan/manifest/setupgit clone --depth 1 https://github.com/iampawan/ManifestWhat 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.00045 | $0.00863 |
| Opus 5 | $0.00023 | $0.00432 |
| Sonnet 5 | $0.00009 | $0.00173 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
setup 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup (alias: /manifest setup)
Configure or check your Manifest setup. Behaves differently based on whether you've set up yet:
- No
.manifest/repos.ymlyet → runs the setup-init wizard: auto-detects your repos, frameworks, event SDKs, and test patterns, asks only what it can't detect, and writes a complete config. Zero placeholders to hand-edit. .manifest/repos.ymlexists → runs the setup-check verifier: reports which MCPs are connected, which scopes are granted, and what each gap would block.
Usage
/setup # auto-routes: init if unconfigured, check if configured
/setup init # force the detection wizard (re-run to add repos)
/setup check # force the verifier
/manifest setup # same as /setup
The init wizard (first run)
- Discovers your repos (from a code-index MCP, or asks you).
- Auto-detects per repo: framework, languages, event SDK, test framework, where API calls live, and (for backends) which route prefixes they own.
- Infers cross-repo API links (which frontend calls which backend).
- Asks ONLY the handful of things it can't detect — e.g., native-vs- Flutter convention, a missing backend repo, your Slack channel.
- Writes a complete
.manifest/repos.ymland creates.manifest/contracts/. - Verifies MCPs + scopes.
- Summarizes and points you at
/contract new.
The check verifier (later runs)
Reports MCP connection status, scope gaps mapped to the commands they'd break, and project-config gaps. See the table it prints for what to connect next.
What it checks
MCPs (required, recommended, optional):
- GitHub (required — code + PR access)
- Sentry (required — errors + releases)
- Slack (required — human gates + daily reports)
- Firebase Analytics / Amplitude (recommended — launch metrics)
- Atlassian / JIRA (recommended — pull contracts from tickets)
- Figma (optional — design coverage)
- DB / Cloud Logging (optional — server-side metric fallbacks)
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 · 104 lines · 45 tokens per session scan A 6d1c77bec28a
setup is a command published in the GitHub repository iampawan/Manifest (5 stars, last pushed 20d ago), licensed MIT. It adds 45 tokens to every session and 863 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.