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/ashtonau/pear-plugin/briefinggit 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.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.00015 | $0.00273 |
| Opus 5 | $0.00008 | $0.00137 |
| Sonnet 5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
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 3d 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 Pear's base tools.
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 - Call
pear_list_remindersfor incomplete reminders - 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
- Reminders listed by priority, showing due dates where set
- 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.
- 3d ago First seen · 24 lines · 0 tokens per session scan A 4fc83bdb2e0c
briefing is a command published in the GitHub repository AshtonAU/pear-plugin (6 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 273 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-31.
Other commands, from other repositories
quick-event
Quickly create a calendar event from natural language when the time and place are already known and stated directly. For deriving an event from a source — a meeting notice, an announcement, a message thread — where the time may have been corrected and the basis should be recorded, use the archive-event skill instead.
remind
Create a reminder from natural language.
week
Show this week's calendar overview.
today
Show today's calendar events and pending reminders.
calendar
View calendars, manage events, and check availability.
contacts
Command "contacts" from nylas/cli, covering contacts management, list contacts, show contact, create contact and update contact.