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.
git clone --depth 1 https://github.com/systemoperators/claude-pluginsWrote 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/commands/systemoperators/claude-plugins/summary)<a href="https://agentmods.dev/commands/systemoperators/claude-plugins/summary"><img src="https://agentmods.dev/badge/commands/systemoperators/claude-plugins/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/commands/systemoperators/claude-plugins/summary"><img src="https://agentmods.dev/badge/commands/systemoperators/claude-plugins/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.00009 | $0.00184 |
| Opus 5.5 | $0.00004 | $0.00074 |
| Sonnet 5.5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
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 1mo 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 the alto.index data source: $ARGUMENTS
Valid sources: notes, reminders, contacts, calendar, messages, granola, voice-memos, safari-bookmarks, safari-history
Steps:
- Check if
~/Documents/alto-index/$ARGUMENTS/exists - If it exists, count the files and read the CLAUDE.md if present
- Provide a summary:
- total number of items
- folder/list breakdown (for notes and reminders)
- date range of content
- notable items or patterns
If $ARGUMENTS is empty or invalid, list the available data sources with file counts.
Keep the summary concise - a few bullets per source, not a full dump.
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.
- 1mo ago First seen · 23 lines · 9 tokens per session scan A 03dde0a99ceb
summary is a command published in the GitHub repository systemoperators/claude-plugins (6 stars, last pushed 8mo ago), licensed MIT. It adds 9 tokens to every session and 184 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.
memory
Read-side memory operations on the knowledge graph: search past decisions and patterns, load session context, view decision timelines, render Mermaid graph visualizations. Subcommands: search, load, history, viz, status. Use when finding or reviewing what memory already holds. For storing new knowledge instead, invoke…
negative-keyword-sweep
Find wasted spend in Google Ads search terms and add negatives at the right scope (account list, campaign, or ad group). Use when the user says "find junk keywords", "stop wasting on bad searches", or wants a search-terms cleanup.
memory-forget
Command "memory-forget" from waittim/MemoryCustodian, covering memory-forget and review the preview, then apply its plan id.
setup
Configure mnemonic for proactive memory operations.
bootstrap
Bootstrap memories from project documentation.