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/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/exec-plan)<a href="https://agentmods.dev/commands/first-fluke/fullstack-starter/exec-plan"><img src="https://agentmods.dev/badge/commands/first-fluke/fullstack-starter/exec-plan/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/first-fluke/fullstack-starter/exec-plan"><img src="https://agentmods.dev/badge/commands/first-fluke/fullstack-starter/exec-plan.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.00020 | $0.00059 |
| Opus 5 | $0.00010 | $0.00030 |
| Sonnet 5 | $0.00004 | $0.00012 |
| Haiku 4.5 | $0.00002 | $0.00006 |
Grade A, and why
exec-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 today.
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
Read and follow .agents/workflows/exec-plan.md step by step.
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.
- today First seen · 8 lines · 20 tokens per session scan A c7c73e3c12ae
exec-plan is a command published in the GitHub repository first-fluke/fullstack-starter (222 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 59 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-09-08.
Other commands, from other repositories
sdlc
Route a task to the next synced SDLC workflow based on current artifacts and repo state.
plan-feature
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
brainstorm-feature
Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
retro-learn
Convert delivery findings into skill, eval, workflow, and documentation improvements.
session-report
Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.