agentmods.dev

rem: Command for Claude Code

.claude/commands/prep-for-task.md

prep-for-task is a command for Claude Code from BRO3886/rem. It costs 0 tokens per session (496 once invoked), scanned A, original, MIT.

A startup checklist for beginning development on the rem project, a macOS Reminders command-line application.

In plain words
What is it for?
Use it at the start of a session to inspect project documentation, source files, dependencies, journals, Git history, and working-tree status.
Why use it?
It gathers the project's rules, recent history, structure, tests, and known issues before implementation begins.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is BRO3886/rem's own configuration. It tells Claude Code how to work on rem 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 rem configures →

not rated 157repo 9d ago A scan 0 tokens original MIT
View source ↗ BRO3886/rem rem.sidv.dev
Reuse

Borrowing it

Nothing to install: this file belongs to BRO3886/rem. 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/BRO3886/rem/main/.claude/commands/prep-for-task.md
Clone the repo
git clone --depth 1 https://github.com/BRO3886/rem

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 prep-for-task

README.md
[![agentmods](https://agentmods.dev/badge/commands/bro3886/rem/prep-for-task/github.svg)](https://agentmods.dev/commands/bro3886/rem/prep-for-task)
Your own site
<a href="https://agentmods.dev/commands/bro3886/rem/prep-for-task"><img src="https://agentmods.dev/badge/commands/bro3886/rem/prep-for-task/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 prep-for-task

Your own site · 80×15
<a href="https://agentmods.dev/commands/bro3886/rem/prep-for-task"><img src="https://agentmods.dev/badge/commands/bro3886/rem/prep-for-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 496 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.00000 $0.00496
Opus 5.5 $0.00000 $0.00198
Sonnet 5.5 $0.00000 $0.00099
Haiku 4.5 $0.00000 $0.00050

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

Security

Grade A, and why

prep-for-task 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 2mo 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.

.claude/commands/prep-for-task.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bootstrap context for a new session on the rem project. Run this BEFORE starting any implementation work.

Instructions

Launch these exploration subagents in parallel to gain comprehensive project context:

Agent 1: Project Overview

Read these files and summarize the project state:

  • CLAUDE.md — architecture, non-negotiables, build/test commands
  • README.md — public API, features, limitations
  • Auto memory — check ~/.claude/projects/ for a directory matching the current working directory (the folder name is the absolute path with / replaced by -). Read memory/MEMORY.md inside it for accumulated patterns and gotchas.
  • go.mod — module name and Go version
  • Run git log --oneline -20 for recent commit history
  • Run git status for working tree state

Agent 2: Codebase Structure

Explore the full directory tree and map out:

  • All Go files in each package (cmd/rem/, cmd/rem/commands/, internal/)
  • Test files
  • go-eventkit dependency version

Agent 3: Journal History

Read journals/ — find the latest journal file and read ALL sessions. Extract:

  • What has been built so far (per session)
  • Key technical gotchas and failures
  • Architectural decisions and their rationale
  • What was deferred and why

After Exploration

Summarize your findings to the user in this format:

## Project State
- Commands implemented: <list>
- Commands remaining: <list>
- go-eventkit version: <version>

## Recent Changes
<last 5 commits, one line each>

## Key Gotchas to Remember
<top 5 technical pitfalls from journals and memory>

## Ready for Task
<confirm context is loaded, ask what to work on>

Rules

  • ALWAYS read CLAUDE.md yourself (not via subagent) before launching any agents — it contains critical project context, hosting info, and conventions that you must internalize directly
  • Use subagents for ALL exploration — maximize parallelism
  • Do NOT write or modify any files during prep
  • Do NOT start implementation until the user gives you a task
  • If a plan file exists at ~/.claude/plans/*.md, read it and mention it in your summary

Read the full file on GitHub · 55 lines

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. 2mo ago First seen · 55 lines · 0 tokens per session scan A cad210e16dfd

Subscribe to this mod's changes

prep-for-task is a command published in the GitHub repository BRO3886/rem (157 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 496 tokens. 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.

clieventkitgomacosreminders
Related

prep-for-task compared with commands from other repositories

prep-for-task next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
prep-for-taskBRO3886/remCommand1579d agoMITA0Claude Code
mailomarshahine/apple-pimCommand685d agoMITA27Claude Code
calendarsomarshahine/apple-pimCommand685d agoMITA18Claude Code
configureomarshahine/apple-pimCommand685d agoMITA13Claude Code
remindersomarshahine/apple-pimCommand685d agoMITA21Claude Code
authorizeomarshahine/apple-pimCommand685d agoMITA17Claude Code
contactsomarshahine/apple-pimCommand685d agoMITA17Claude Code