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/lichamnesia/lich-skills/wiki-aggregatenpx skills add LichAmnesia/lich-skills --skill wiki-aggregategit clone --depth 1 https://github.com/LichAmnesia/lich-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/lichamnesia/lich-skills/wiki-aggregate)<a href="https://agentmods.dev/skills/lichamnesia/lich-skills/wiki-aggregate"><img src="https://agentmods.dev/badge/skills/lichamnesia/lich-skills/wiki-aggregate.svg" alt="Measured on agentmods" 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.00103 | $0.02758 |
| Opus 5 | $0.00051 | $0.01379 |
| Sonnet 5 | $0.00021 | $0.00552 |
| Haiku 4.5 | $0.00010 | $0.00276 |
Grade A, and why
wiki-aggregate 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.
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Aggregate — N raw sources → 1 structured pack
A protocol for agentic aggregation of long-horizon research material. Inverts the standard "concat all → ask LLM to summarize" pipeline: instead, an aggregator agent navigates the N source files with three tools, building a notes scratchpad with full path:line provenance, and finally writes a structured pack (brief / findings / sources / aggregation log).
Core principle: don't read everything upfront. Don't merge final answers. Treat the N sources as a queryable environment.
Why this exists
Three traditional ways to aggregate N parallel research outputs all fail on long-horizon, open-ended tasks:
❌ concat all sources into one prompt
→ 200K+ token explosion, attention collapse on long context
❌ summarize each, then merge summaries
→ ~90% of intermediate evidence (the "I noticed X but..." asides) is lost
❌ LLM-as-judge picks the single best source
→ discards the other N-1 sources' independent findings
These failure modes show up clearly on open-ended research tasks where there's no ground-truth verifier. The alternative: treat the N sources as an environment, send a lite agent in to inspect / search / synthesize on demand. Cost ≈ a single rollout, recall is materially higher, and cross-source contradictions get surfaced explicitly.
This skill is the protocol. No Python, no MCP — pure markdown protocol that any harness with Read + Grep can execute.
When to Use
- You have 3-30 raw notes / transcripts / research dumps on one topic, scattered across files
- The current pack on this topic feels thin or you suspect raw evidence wasn't fully lifted
- You want claims with
path:lineprovenance, not vibes - You want cross-source contradictions surfaced, not buried
When NOT to Use
- N < 3 sources — protocol overhead exceeds value, just write a summary by hand
- N > 30 — budget will be exhausted; narrow the scope or batch by sub-topic
- Sources are not yet collected — this is a synthesis tool, not a research tool. Run your collectors first.
- You only need a one-shot Q&A — use a reactive
wiki-ask-style skill instead
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 · 244 lines · 103 tokens per session scan A 6c48ead20aac
wiki-aggregate is a skill published in the GitHub repository LichAmnesia/lich-skills (233 stars, last pushed 2mo ago), licensed MIT. It adds 103 tokens to every session and 2,758 once invoked, about $0.0005 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
gws-gmail-send
Skill "gws-gmail-send" from googleworkspace/cli, covering gmail +send, usage, flags, examples and tips.
gws-shared
The gws binary must be on $PATH. See the project README for install options.
gws-sheets
Google Sheets: Read and write spreadsheets.
gws-gmail
Gmail: Send, read, and manage email.
gws-modelarmor-create-template
Google Model Armor: Create a new Model Armor template.
gws-modelarmor
Google Model Armor: Filter user-generated content for safety.