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/Amey-Thakur/AI-SKILLSWrote 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/amey-thakur/ai-skills/exec-one-pager)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/exec-one-pager"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/exec-one-pager/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/amey-thakur/ai-skills/exec-one-pager"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/exec-one-pager.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.00023 | $0.00362 |
| Opus 5 | $0.00012 | $0.00181 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
exec-one-pager 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 6d 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
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Write an executive one-pager on:
{topic}
Details: {details}
Structure (bottom-line-up-front, fits on one page):
- The ask / bottom line, first: what you want the reader to decide, approve, or know, in the first two sentences. Executives read the top and skim the rest; bury the ask and it dies.
- The situation: the context and why this matters now, briefly.
- The recommendation and the reasoning: what you propose and the 2-3 strongest reasons, with the evidence (numbers, not adjectives).
- The options and tradeoffs, if it is a decision: the alternatives and why yours wins, honestly including its cost.
- What you need: the specific decision, resource, or approval, and by when.
Rules: lead with the conclusion, not the journey (the opposite of building suspense). Ruthlessly concise: one page, every sentence earning its place, no background the reader does not need. Quantify (executives trust numbers, not "significant improvement"). Anticipate the obvious objection and address it. Honest about risk and cost: a one-pager that hides the downside gets found out in the meeting. If a key number is missing, mark it as needed.
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.
- 6d ago First seen · 39 lines · 23 tokens per session scan A 4d21fa581d68
exec-one-pager is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 362 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-03.
Other commands, from other repositories
close
They operate it without you.
burndown-full
Drive a partially-executed plan to 100% coverage across the whole repo — enumerate, batch-execute, prove completeness.
create-ticket
Create a work-item ticket (GitHub issue / Jira) from an existing requirements.md, then promote its draft spec folder to docs/specs/ /.
work-status
Report the current status of a work item by reading its spec files (requirements/design/tasks) and execution log. Read-only.
/opsx-apply
Implement tasks from an OpenSpec change (Experimental).
align
Align cross-functional stakeholders.