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/AshtonAU/pear-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/ashtonau/pear-plugin/briefing)<a href="https://agentmods.dev/commands/ashtonau/pear-plugin/briefing"><img src="https://agentmods.dev/badge/commands/ashtonau/pear-plugin/briefing/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/ashtonau/pear-plugin/briefing"><img src="https://agentmods.dev/badge/commands/ashtonau/pear-plugin/briefing.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.00000 | $0.00343 |
| Opus 5.5 | $0.00000 | $0.00137 |
| Sonnet 5.5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
briefing 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.
What it actually says
Build a daily briefing using tools exposed by the connected client. Do not call tools that are unavailable to this account.
If the user provided a date argument, use it. Otherwise default to today. If the user provided a timezone argument, use it. Otherwise try to infer from context or omit.
- Call
pear_list_eventsfor the chosen day - If legacy reminder access is relevant and the tool is available, call
pear_list_remindersfor incomplete legacy reminders. Explain that Pear cannot read Apple's upgraded Reminders store. If Apple returns migration placeholders or no legacy data, do not imply the user has no current tasks - If Mail is likely relevant, call
pear_list_emailsonINBOXwithunreadOnly: trueand a small limit
Present the briefing in a clear, scannable format:
- Date and day of week as a header
- Events listed chronologically with times, titles, locations, and attendee names
- Legacy reminders listed by priority, showing due dates where set; state the compatibility limitation when current Apple reminders are unavailable
- Unread Mail only if you checked it and found relevant messages
- A brief natural-language summary at the end (e.g., "You have 3 meetings, 5 pending tasks, and 2 unread emails today")
ARGUMENTS: $ARGUMENTS
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 Changed 28d73360150d
- 1mo ago First seen · 24 lines · 0 tokens per session scan A 4fc83bdb2e0c
briefing is a command published in the GitHub repository AshtonAU/pear-plugin (7 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 343 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-31.
Other commands, from other repositories
rename
Generate a concise, sentence-case title (3-7 words) that captures the main topic or goal of this coding session. The title should be clear enough that the user recognizes the session in a list. Use sentence case: capitalize only the first word and proper nouns.
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
help
Explain Ralph Wiggum technique and available commands.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.