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/armoin2018/ai-leyWrote 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/armoin2018/ai-ley/build-launch-plan)<a href="https://agentmods.dev/commands/armoin2018/ai-ley/build-launch-plan"><img src="https://agentmods.dev/badge/commands/armoin2018/ai-ley/build-launch-plan.svg" alt="Measured on agentmods" 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.00014 | $0.00159 |
| Opus 5 | $0.00007 | $0.00079 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
build-launch-plan 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 8d 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
Build Launch Plan Command
- Follow the prompt instructions found in
.ai-ley/shared/prompts/build-launch-plan.md
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.
- 8d ago First seen · 21 lines · 14 tokens per session scan A 195cc9131cc9
build-launch-plan is a command published in the GitHub repository armoin2018/ai-ley (11 stars, last pushed 7mo ago), licensed CC0-1.0. It adds 14 tokens to every session and 159 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
retention-report
Monthly retention readout — NRR, GRR, churn by reason, and expansion, from the customer book in one page.
midday-checkin
Mid-day reset — what's done, what's slipping, what to protect this afternoon.
feature-development
Workflow command scaffold for feature-development in marketing-council-pack.
validate
A five-question validation command for judging whether a competitor's product idea is worth pursuing. It checks traffic, revenue evidence, the competitor's main paid feature, build difficulty, and a possible way to reach users.
deploy
A deployment command for publishing a website through GitHub and Vercel, then connecting a custom domain. GitHub stores the code, while Vercel builds and hosts the site.
launch
A launch checklist for taking the first real step in one chosen traffic channel, such as search ads, social media, or SEO.