mcp-apple-reminders: Command for Claude Code

.claude/commands/implement-slice.md

implement-slice is a command for Claude Code from rex/mcp-apple-reminders. It costs 7 tokens per session (164 once invoked), scanned A, original, MIT.

A command that carries out one planned slice of work listed in TASK_STATE.md. It then runs tests and reviews the resulting code before reporting the outcomes.

In plain words
What is it for?
Use it to implement one specific task slice, verify it with tests, and receive a review without automatically starting the next slice.
Why use it?
It prevents work from moving ahead when an earlier required slice is unfinished. It also separates implementation, testing, and review for each piece of a task.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions subagents.

This is rex/mcp-apple-reminders's own configuration. It tells Claude Code how to work on mcp-apple-reminders itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-apple-reminders configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rex/mcp-apple-reminders. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rex/mcp-apple-reminders/main/.claude/commands/implement-slice.md
Clone the repo
git clone --depth 1 https://github.com/rex/mcp-apple-reminders

Made for: Claude Code.

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.

agentmods badge for implement-slice

README.md
[![agentmods](https://agentmods.dev/badge/commands/rex/mcp-apple-reminders/implement-slice/github.svg)](https://agentmods.dev/commands/rex/mcp-apple-reminders/implement-slice)
Your own site
<a href="https://agentmods.dev/commands/rex/mcp-apple-reminders/implement-slice"><img src="https://agentmods.dev/badge/commands/rex/mcp-apple-reminders/implement-slice/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.

agentmods 80×15 button for implement-slice

Your own site · 80×15
<a href="https://agentmods.dev/commands/rex/mcp-apple-reminders/implement-slice"><img src="https://agentmods.dev/badge/commands/rex/mcp-apple-reminders/implement-slice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 164 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.00164
Opus 5.5 $0.00003 $0.00066
Sonnet 5.5 $0.00001 $0.00033
Haiku 4.5 $0.00001 $0.00016

Measured 1mo ago against content hash bb4eeda00c6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement-slice 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/implement-slice.md · 18 lines

What it actually says

Execute slice $ARGUMENTS.

  1. Read TASK_STATE.md, locate the slice.
  2. If not found, or if prior required slices are unchecked → STOP.
  3. Spawn implementer subagent with the slice ID.
  4. Then spawn test-runner to verify.
  5. If tests pass, spawn reviewer on the diff.
  6. Report all three outputs (implementer summary, test result, review verdict).

Do NOT proceed to the next slice. Each slice gets its own invocation.

Changes

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.

  1. 1mo ago First seen · 18 lines · 7 tokens per session scan A bb4eeda00c6f

Subscribe to this mod's changes

implement-slice is a command published in the GitHub repository rex/mcp-apple-reminders (3 stars, last pushed 25d ago), licensed MIT. It adds 7 tokens to every session and 164 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.