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/davidroliverba/architectkb/exec-summarynpx skills add DavidROliverBA/ArchitectKB --skill exec-summarygit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWhat 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.00009 | $0.01252 |
| Opus 5 | $0.00005 | $0.00626 |
| Sonnet 5 | $0.00002 | $0.00250 |
| Haiku 4.5 | $0.00001 | $0.00125 |
Grade A, and why
exec-summary 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/exec-summary Skill
Generate a non-technical executive summary from technical ADRs, Pages, or Project notes.
Purpose
Translate technical architecture content for non-technical stakeholders. Useful for:
- Board presentations
- Stakeholder updates
- Management briefings
- Cross-team communication
Usage
/exec-summary "ADR - API Gateway Selection"
/exec-summary "Project - AIIncidentProcessor" exec
/exec-summary "Page - Kafka Integration" manager
Instructions
-
Read the source note completely
-
Identify the audience (default: exec):
exec- C-suite, board level (business impact, risk, cost)manager- Department heads (operational impact, timeline, resources)stakeholder- Project stakeholders (what changes, how affects them)
-
Extract key information:
For ADRs:
- What decision was made (one sentence)
- Why it matters to the business
- What it costs / saves
- Key risks and mitigations
- Timeline / when it takes effect
For Projects:
- What the project delivers
- Business benefit
- Current status (RAG)
- Key milestones
- Resources / budget
For Pages:
- What this document describes
- Why it matters
- Key takeaways
- Actions required (if any)
-
Generate summary using this template:
# Executive Summary: {{Title}}
**Generated:** {{date}}
**Source:** [[{{source note}}]]
**Audience:** {{audience}}
---
## One-Line Summary
{{Single sentence explaining what this is about in business terms}}
## Why This Matters
{{2-3 sentences on business impact - avoid technical jargon}}
## Key Points
- {{Point 1 - business language}}
- {{Point 2 - business language}}
- {{Point 3 - business language}}
## Impact
| Area | Impact |
|------|--------|
| **Cost** | {{cost impact or "No direct cost impact"}} |
| **Timeline** | {{when does this happen}} |
| **Risk** | {{key risk in plain language}} |
| **Benefit** | {{main business benefit}} |
## Recommendation / Decision
{{What was decided or what action is recommended - one paragraph}}
## Questions This Answers
- {{Question a stakeholder might ask}}
- {{Another likely question}}
---
*This summary was generated from technical documentation. For full details, see [[{{source note}}]].*
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 · 215 lines · 9 tokens per session scan A 8ba9fa5b5483
exec-summary is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,252 once invoked, about $0.0000 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.