Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/pivoshenko/pivoshenko.ai/wiki-summarize)<a href="https://agentmods.dev/skills/pivoshenko/pivoshenko.ai/wiki-summarize"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/wiki-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/pivoshenko/pivoshenko.ai/wiki-summarize"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/wiki-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.00109 | $0.00520 |
| Opus 5 | $0.00055 | $0.00260 |
| Sonnet 5 | $0.00022 | $0.00104 |
| Haiku 4.5 | $0.00011 | $0.00052 |
Grade A, and why
wiki-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 10d 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
Wiki summarize
Vault: /Users/volodymyr.pivoshenko/Library/Mobile Documents/iCloud~md~obsidian/Documents/Vault
Rough input -> polished source note. The user dumps; this skill structures.
Flow
- Read vault
CLAUDE.md+INDEX.mdfirst. - Gather: user notes as the base. URL given -> fetch page/transcript for metadata + gaps. User notes win over fetched content on emphasis — summarize what they found valuable.
- New note in
05 SOURCES/from99 TEMPLATES/Source.md. Filename = clean title of the source, Title Case. - Shape (proven by existing notes — match it exactly):
## Source— speaker/author + link## Summary— 2–4 sentence overview## Key Insights— bullets,**Bold insight title**. Explanationform, substance over count## References— books/tools/links mentioned, only if any
- Frontmatter:
type: source,source_type: talk|book|article|video|paper,url,author, dates, tags.ratingonly if user gave a verdict. - Distill: update EVERY existing concept page this source touches — new info goes into the page, contradictions flagged inline (
> [!warning] Contradicts ...). New concepts worth keeping -> stubs in02 PERMANENT NOTES. Wikilink all of them from the insights. - Duties: INDEX.md + LOG.md + report.
Rules
- Don't pad. Thin source -> short note. Never invent insights not in the material.
- Long book -> insights grouped by theme, still one note.
- Same source already in INDEX.md -> update existing note 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.
- 10d ago First seen · 33 lines · 109 tokens per session scan A 21f8ac7364ac
wiki-summarize is a skill published in the GitHub repository pivoshenko/pivoshenko.ai (4 stars, last pushed yesterday), licensed MIT. It adds 109 tokens to every session and 520 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-31.
Other skills, from other repositories
80-livekit-agents-majiayu000-claude-skill-registr
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
agent-creation-skill
Procedural guide for creating new agents from templates when project complexity requires delegation.
agent-creator
Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use…
semantic-persona-routing
Erstellt und verwendet einen anbieterneutralen semantischen Routing-Graphen aus Personas, koordinierenden Rollen, Experten und aktiven Skill-Endpunkten. Verwenden, wenn ein LLM eine Anfrage von einer Leitrolle über einen Experten zu einem Skill routen, aus einem vorhandenen Agentensystem einen portablen Persona-Router…
80-livekit-agents-panaversity-agentfactory-1f8ecf89
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
agent-creator
Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use…