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 commands/spillwavesolutions/automating-mac-apps-plugin/contact-upsertgit clone --depth 1 https://github.com/SpillwaveSolutions/automating-mac-apps-pluginWrote 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/spillwavesolutions/automating-mac-apps-plugin/contact-upsert)<a href="https://agentmods.dev/commands/spillwavesolutions/automating-mac-apps-plugin/contact-upsert"><img src="https://agentmods.dev/badge/commands/spillwavesolutions/automating-mac-apps-plugin/contact-upsert.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 | $0.00014 | $0.00320 |
| Opus 5 | $0.00007 | $0.00160 |
| Sonnet 5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
contact-upsert 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 5d 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
Contact Upsert
Creates or updates a contact by email, sets core fields, and ensures group membership.
Usage
/contact-upsert --name "Ada Lovelace" --email [email protected] \
--phone "+1-555-123-4567" --organization "Analytical Engine" \
--title "Engineer" --groups "VIP,Engineering"
Behavior
- Finds an existing contact by email (server-side filter).
- If found, updates name/org/title/phone; if not, creates a new contact.
- Adds email/phone as multi-value elements (no overwrite of other values).
- Ensures membership in the provided groups (creates groups if missing).
- Saves changes via Contacts.
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.
- 5d ago First seen · 45 lines · 14 tokens per session scan A 038e810302ba
contact-upsert is a command published in the GitHub repository SpillwaveSolutions/automating-mac-apps-plugin (40 stars, last pushed 13d ago), licensed MIT. It adds 14 tokens to every session and 320 once invoked, about $0.0001 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 commands, from other repositories
start
Analyze this project and build a GoalT goal tree for it, linking real files and backend artifacts to each goal.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.
blueprint
Generate an implementation plan with system architecture design and dependency-ordered task breakdown from a specification.
specify
Create specs from project briefs with acceptance criteria and testable requirements.
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.