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 skills add DavidROliverBA/ArchitectKB --skill summarizegit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/skills/davidroliverba/architectkb/summarize)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/summarize"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/summarize/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/skills/davidroliverba/architectkb/summarize"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/summarize.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.00000 | $0.00460 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
summarize 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 9d 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
/summarize
Summarize a note or set of notes.
Usage
/summarize <note name>
/summarize Meeting - 2025-01-05 MyDataIntegration Review
/summarize all meetings about CloudMigration
/summarize last 5 meetings
Instructions
Single Note Summary
- Find the note by name (fuzzy match if needed)
- Read the full content
- Generate summary:
# Summary: {{note title}}
**Type**: {{type}}
**Date**: {{date if applicable}}
## Key Points
- {{main point 1}}
- {{main point 2}}
- {{main point 3}}
## Decisions Made
- {{decision 1}}
## Action Items
- [ ] {{action 1}}
- [ ] {{action 2}}
## People Involved
{{attendees or people mentioned}}
## Related Notes
{{suggest related notes based on content}}
Multiple Notes Summary (use sub-agents)
For "all meetings about X" or "last N meetings":
Phase 1: Planning
- Identify which notes to summarize
- Create list of files to process
Phase 2: Parallel Processing
Launch sub-agents using model: "haiku" for efficiency:
- Launch sub-agent per note (max 5 parallel)
- Each agent extracts: key points, decisions, actions
Phase 3: Synthesis
# Summary: {{description of note set}}
**Notes Analysed**: {{count}}
**Date Range**: {{earliest}} to {{latest}}
## Executive Summary
{{2-3 paragraph synthesis of all notes}}
## Key Themes
1. **{{theme 1}}**: {{explanation}}
2. **{{theme 2}}**: {{explanation}}
## All Decisions
| Date | Source | Decision |
| ---- | ------ | -------- |
{{consolidated decisions}}
## Outstanding Actions
| Action | From | Assigned | Due |
| ------ | ---- | -------- | --- |
{{consolidated actions}}
## Progression
{{how topics evolved across the notes}}
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.
- 9d ago First seen · 106 lines · 0 tokens per session scan A 7fb0357bfb42
summarize is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 460 tokens. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…