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/contacts)<a href="https://agentmods.dev/commands/systemoperators/claude-plugins/contacts"><img src="https://agentmods.dev/badge/commands/systemoperators/claude-plugins/contacts/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/contacts"><img src="https://agentmods.dev/badge/commands/systemoperators/claude-plugins/contacts.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.00005 | $0.00128 |
| Opus 5.5 | $0.00002 | $0.00051 |
| Sonnet 5.5 | $0.00001 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
contacts 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
Work with Apple Contacts synced to ~/Documents/alto-index/contacts/.
If $ARGUMENTS is provided, search for that contact by name using Glob and Grep. Show their full details: phone numbers, emails, addresses, organization, birthday, notes.
If no arguments, show a count of total contacts and list a few recent ones.
Always include the addressbook:// deep link from the link frontmatter field so the user can open the contact in the native app.
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 · 14 lines · 5 tokens per session scan A a2e08d7308b8
contacts is a command published in the GitHub repository systemoperators/claude-plugins (6 stars, last pushed 8mo ago), licensed MIT. It adds 5 tokens to every session and 128 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
do-task
Do an ad-hoc, tactical task on a work item with NO PDLC process — no spec chain, no phase gates, no review chain. Work, ask follow-ups on the thread, continue until the requester says it is done.
on
Turn on senior mode — refuses vague questions, hints instead of answers, never writes code.
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
firm
Convene your standing AI staff — memos on every beat, a board session without you, minutes with dissent preserved.
promote
The promote loop — scan your transcripts for what you keep asking, pick a pattern, draft the skill, test its triggers, publish the release package.
ship-a-feature
Workflow recipe — take a feature idea from fuzzy brief to launch plan by chaining 5 skills.