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 britt/agent-skills --skill consolidate-notes-summarygit clone --depth 1 https://github.com/britt/agent-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/skills/britt/agent-skills/consolidate-notes-summary)<a href="https://agentmods.dev/skills/britt/agent-skills/consolidate-notes-summary"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/consolidate-notes-summary/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/britt/agent-skills/consolidate-notes-summary"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/consolidate-notes-summary.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.00057 | $0.00714 |
| Opus 5 | $0.00028 | $0.00357 |
| Sonnet 5 | $0.00011 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
consolidate-notes-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 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consolidate Notes Summary Skill
Search project notes by topic or tag and produce a consolidated summary that synthesizes information across multiple sources.
Notes location: check for a notes/ or docs/notes/ directory, a vault path noted in CLAUDE.md, or ask the user; search with Grep across that directory.
When to Use
Activate when:
- Gathering scattered knowledge on a topic
- Preparing a summary from multiple note sources
- Reviewing what's been documented about a subject
- Identifying gaps in documentation
When NOT to use: single-note summarization (just read it), or consolidating code documentation rather than notes.
Workflow
- Locate the notes directory (see notes location above); confirm with the user if ambiguous.
- Search by topic or tag with Grep across the directory, including synonyms, abbreviations, and related terms (e.g. "auth" as well as "authentication", tag forms like
#auth). Case-insensitive matching catches more hits. - Read the matching notes, capturing dates, authors, and key claims from each.
- Synthesize the findings per the Synthesis vs. Aggregation guidelines below — combine, don't concatenate.
- Emit the output template, filling every section and flagging anything you could not determine.
If the search returns nothing, widen terms once before reporting back; if it still finds nothing, say so plainly and list the terms tried rather than fabricating a summary.
Output Structure
## Consolidated: [Topic]
**Sources**: [X notes reviewed] | **Date Range**: [earliest] to [latest]
### Summary
[Synthesized overview combining insights from all related notes]
### Key Points
- [Point 1] — from [note reference]
- [Point 2] — from [note reference]
- [Point 3] — from [note reference]
### Timeline
| Date | Event/Decision |
|------|----------------|
| [Date] | [What happened] |
### Cross-References
- **[Note 1 title]**: [how it relates to the topic]
- **[Note 2 title]**: [how it relates]
### Gaps
- [Information that's missing]
- [Topics that need more documentation]
- [Outdated content that needs refresh]
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 · 94 lines · 57 tokens per session scan A 5e8a97a510b8
consolidate-notes-summary is a skill published in the GitHub repository britt/agent-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 57 tokens to every session and 714 once invoked, about $0.0003 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.