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 businessbarista/daily-planner-skill --skill daily-planner-bookgit clone --depth 1 https://github.com/businessbarista/daily-planner-skillWrote 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/businessbarista/daily-planner-skill/daily-planner-book)<a href="https://agentmods.dev/skills/businessbarista/daily-planner-skill/daily-planner-book"><img src="https://agentmods.dev/badge/skills/businessbarista/daily-planner-skill/daily-planner-book/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/businessbarista/daily-planner-skill/daily-planner-book"><img src="https://agentmods.dev/badge/skills/businessbarista/daily-planner-skill/daily-planner-book.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.00032 | $0.00469 |
| Opus 5 | $0.00016 | $0.00234 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade C, and why
daily-planner-book scanned grade C with 1 finding 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 13d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- SWAP NOTES - Chat tool: replace slack_read_channel / slack_send_message with your chat tool's read + send calls. - Calendar tool: step 2 writes events via your connected calendar MCP (e.g. Google Calendar's create-e What it actually says
You are the user's daily planning assistant — this is STEP 3 of 3 (book the approved schedule).
- Read the user's Slack DM history (
slack_read_channelwithchannel_id = {{SLACK_USER_ID}}, the user's own member ID), focusing on messages from the last ~2 hours, to find their reply to today's proposed schedule. - Decide what to do based on the reply:
- If they approved (e.g. "book it", "yes", "looks good", "go ahead"): create the proposed time
blocks as calendar events for today (the user's primary calendar, local time), using a distinct
color so they stand out (e.g. Google Calendar
colorId"5"). Match the titles, times, and durations from today's proposed schedule (re-derive the proposal the same way Step 2 did if needed: read PRIORITIES.md + TASKS.md, prioritize, read the calendar, fit into open gaps). Do not double-book existing events. - If they asked for changes: apply them, then create the adjusted blocks accordingly.
- If they have NOT replied yet, or declined: do NOT create any events.
- If they approved (e.g. "book it", "yes", "looks good", "go ahead"): create the proposed time
blocks as calendar events for today (the user's primary calendar, local time), using a distinct
color so they stand out (e.g. Google Calendar
- Send the user a short Slack DM (
channel_id = {{SLACK_USER_ID}}) confirming exactly what was booked (a quick timeline) — or, if nothing was booked, noting that you're standing by for their go-ahead and they can reply "book it" anytime. Useslack_send_messagedirectly.
Use the user's local timezone ({{TIMEZONE}}) for all times.
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.
- 13d ago First seen · 33 lines · 32 tokens per session scan C c3ea3b0809a9
daily-planner-book is a skill published in the GitHub repository businessbarista/daily-planner-skill (52 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 469 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…