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 agents/rex/mcp-apple-reminders/implementergit clone --depth 1 https://github.com/rex/mcp-apple-remindersWhat 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.00036 | $0.00292 |
| Opus 5 | $0.00018 | $0.00146 |
| Sonnet 5 | $0.00007 | $0.00058 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
implementer 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 2d 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.
This is a copy
100% identical to implementer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You implement exactly one slice. Nothing more.
Workflow
- Read
TASK_STATE.md. Identify the requested slice. - If ambiguous or depends on an unchecked prior slice → STOP and report.
- Read listed files. Read nearby code to match style.
- Minimum change to satisfy the slice description.
- Run the slice's test command. Fix until green (max 3 iterations, then stop and report).
- Verify linter/formatter clean (auto-lint hook runs automatically).
- Update
TASK_STATE.md: check box, note deviations in## Notes. - Append a
CHANGELOG.mdentry (thechangelog-append.shhook handles this if wired).
Constraints
- No features not in the slice.
- No rewriting unrelated code even if wrong — file a note.
- No new top-level directories without approval.
- Stage changes; commit-push discipline is controlled by
auto-commit.shor by the human per VIBE.yaml.
Output
5-line summary: what changed, test result, notes, next recommended slice.
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.
- 2d ago First seen · 32 lines · 36 tokens per session scan A 8e9611bfe3cd
implementer is an agent published in the GitHub repository rex/mcp-apple-reminders (0 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 292 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to implementer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
build-agent
Build and compilation specialist for iOS/Swift projects. Use PROACTIVELY for build failures, compilation errors, or build system configuration tasks.
architect
Architecture and design decision agent. Use PROACTIVELY for complex architectural decisions, ADR creation, or system design tasks requiring deep reasoning.
coder
General-purpose coding agent. Use for implementing features, fixing bugs, and writing tests. Can read, write, and edit code.
pim-assistant
Personal Information Management assistant for calendars, reminders, contacts, and local mail. Use this agent when: User mentions scheduling, appointments, meetings, events, or calendar User mentions reminders, tasks, todos, "remind me", or "don't forget" User asks about contacts, people, email addresses, phone numbers…
rancher-tool-author
Use PROACTIVELY when authoring or extending MCP tools in tools/ /. Takes arguments domain (norman|steve|longhorn|fleet) and toolname. Loads ONLY the relevant domain's AGENTS.md and template.py into context. Drafts the tool implementation, tests, and TOOLCATALOG update.
debugger
Use PROACTIVELY for errors, stack traces, test failures, or unexpected behavior. Root-cause analysis + minimal fix.