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 skills/billbuchanan-code/claude-code-power-setup/exec-briefnpx skills add billbuchanan-code/claude-code-power-setup --skill exec-briefgit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWhat 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.00012 | $0.00465 |
| Opus 5 | $0.00006 | $0.00233 |
| Sonnet 5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
exec-brief 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 yesterday.
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
Executive Brief
Transform raw data, analysis, or research output into a concise 1-page executive summary suitable for C-suite review.
Process
-
Parse the input from $ARGUMENTS. Accept:
- A file path to raw data or analysis
- Inline text pasted by the user
- A reference to output from a previous agent or skill
-
If the input is a file path, read it. If multiple files are referenced, read all of them.
-
Extract key findings by identifying:
- The core question or problem being addressed
- The 3 most significant data points or conclusions
- Any metrics, dollar amounts, or percentages that support findings
- Risks or caveats that decision-makers must know
-
Structure the brief using this exact format:
Situation
2-3 sentences. What prompted this analysis and what was examined.
Key Findings
Exactly 3 findings, each as a bolded heading with 1-2 supporting sentences. Every finding must include at least one metric or specific data point sourced from the input.
Recommendation
1-2 sentences. The single clearest action to take, with expected outcome.
Risk
1-2 sentences. The primary risk of acting (or not acting), with likelihood/impact if available.
Supporting Detail
3-5 bullet points of secondary findings or context for those who want to dig deeper.
Quality Rules
- No paragraph longer than 3 sentences
- Every claim must be traceable to the input data — no fabrication
- Target length: 300-400 words
- Use specific numbers, not vague qualifiers ("revenue increased 23%" not "revenue increased significantly")
- Use ISO 8601 dates where dates appear
- Label any inference or assumption explicitly
Output Format
Present the brief in clean markdown, ready to share. Follow the brief with a single metadata line:
Source: [input file name or "inline data"] | Word count: [N] | Date: [YYYY-MM-DD]
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.
- yesterday First seen · 63 lines · 12 tokens per session scan A 9056334ef225
exec-brief is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 465 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…