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 skills add jrgilbertson/the-rookery --skill reviewing-meetingsgit clone --depth 1 https://github.com/jrgilbertson/the-rookeryWrote 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/skills/jrgilbertson/the-rookery/reviewing-meetings)<a href="https://agentmods.dev/skills/jrgilbertson/the-rookery/reviewing-meetings"><img src="https://agentmods.dev/badge/skills/jrgilbertson/the-rookery/reviewing-meetings/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/skills/jrgilbertson/the-rookery/reviewing-meetings"><img src="https://agentmods.dev/badge/skills/jrgilbertson/the-rookery/reviewing-meetings.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.00111 | $0.01738 |
| Opus 5 | $0.00056 | $0.00869 |
| Sonnet 5 | $0.00022 | $0.00348 |
| Haiku 4.5 | $0.00011 | $0.00174 |
Grade A, and why
reviewing-meetings 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing Meetings
Turn completed meetings from the configured source into grounded proposals for review. Granola is one supported source, not part of the workflow's identity. Scheduled and manual entry use this same workflow. A schedule supplies timing, not extra authority: every run remains read-only until the user reviews a proposal.
Resolve visible action responses first
Before choosing a source scope, determine whether the current user message only approves, edits, defers, skips, declines, revisits, or otherwise decides actions from a visible meeting-review bundle. If so, read references/applying-approved-actions.md and handle that response directly. Do not rediscover meetings, run a broad meeting-source query, or append unrelated proposals. When application-time revalidation of an exact CRM-derived action requires evidence from its original meeting, the workflow may reread only the smallest necessary slice from the exact displayed source and native ID. This bounded reread is not discovery and must not produce another meeting or proposal. If the source read is unavailable or fails, or the exact source or native ID is ambiguous, make no write and report that action Manual.
If the same message also explicitly asks for a new meeting check, finish the action-response phase first. Then run discovery as a separate read-only phase; do not use newly discovered proposals to reinterpret the earlier action decision.
Completion: a response to visible actions was handled against that exact bundle before any separately requested discovery began.
Select the source scope
For a manual request, use the named meeting or time range. If neither is given, use the inclusive 168-hour interval ending at the query time. For a scheduled request, use the supplied range or the same 168-hour default. Compare boundary times as absolute instants. The overlap is intentional because eligibility comes from observable source state, not a last-run cursor.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 172 lines · 111 tokens per session scan A 38c46fe83e9c
reviewing-meetings is a skill published in the GitHub repository jrgilbertson/the-rookery (5 stars, last pushed today), licensed MIT. It adds 111 tokens to every session and 1,738 once invoked, about $0.0006 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 skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
accint-commitments
Triage acc's open promises and close them with honest real-world verdicts via accact(runtime="outcome").
peon-ping-toggle
Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
slack-messaging
Use when writing, drafting, scheduling, or improving a Slack message, announcement, or reply sent via the Slack MCP tools (slacksendmessage, slacksendmessagedraft, slackschedulemessage). Covers Slack markdown formatting, message structure, thread etiquette, reactions, and scheduling, and points to the right dialect…