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/launchgit 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.00047 | $0.00393 |
| Opus 5 | $0.00023 | $0.00197 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
launch 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
/launch [--day N]
Invokes the launch-report skill against the given contract.
Usage
/launch SC-005 # auto-detects current day index
/launch SC-005 --day 7 # force a day-7 style report
/launch SC-005 --day 28 # final verdict
What it does
- Reads the contract and latest revision.
- Auto-detects the best measurement source: Firebase Analytics → Amplitude → server logs → DB query → Sentry release data → manual input. Uses the richest available.
- Pulls errors from Sentry.
- Pulls qualitative signals from JIRA, support tools, Slack (if connected).
- Computes a verdict:
landed | partial | not-landed | rolled-back | unmeasurable-quant. - Writes
.manifest/contracts/<ID>.launch-report-day<N>.mdwith a Cycle Time section showing intake → prod duration. - Posts a 3-line summary to the contract's Slack thread.
- Updates the contract's
landingTrackarray andslaHitfield.
When to use manually
- Spot-checking a feature mid-window.
- Generating an ad-hoc report for stakeholders.
- Re-running after a data issue is resolved.
For the standard cadence (day 1/7/14/28), the launch-monitor.yml
cron handles it automatically.
Output
A markdown report at .manifest/contracts/<ID>.launch-report-day<N>.md
and a Slack message with the verdict line.
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 · 47 lines · 47 tokens per session scan A c15cff21433c
launch is a command published in the GitHub repository iampawan/Manifest (5 stars, last pushed 20d ago), licensed MIT. It adds 47 tokens to every session and 393 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.