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 skills/mpazik/binder/day-next-plannpx skills add mpazik/Binder --skill day-next-plangit clone --depth 1 https://github.com/mpazik/BinderWrote 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/mpazik/binder/day-next-plan)<a href="https://agentmods.dev/skills/mpazik/binder/day-next-plan"><img src="https://agentmods.dev/badge/skills/mpazik/binder/day-next-plan.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.1 | $0.00017 | $0.00654 |
| Opus 5 | $0.00009 | $0.00327 |
| Sonnet 5 | $0.00003 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
day-next-plan 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 6d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build the target day's plan. The source day's summary is already done — skip straight to carry-forward review.
Context
Offset controls direction: proactive (positive or default — planning days ahead) or retroactive (negative — backfilling a past day's plan).
Source day = carry-forward source (offset $0). Target day = day being planned (offset $0 + 1). Always read its date from the entry below — never assume it's "tomorrow."
Source day entry (carry-forward review): !O=$0; binder read $(bun scripts/journal.ts d ${O:-0} --key) --format yaml
Target day entry (we are planning this — created if missing): !O=$0; binder read $(bun scripts/journal.ts d $((${O:-0} + 1)) --key) --format yaml
Week context: !O=$0; binder read $(bun scripts/journal.ts w ${O:-0} --key) -f "weekPeriod,goal,plan,achievements" --format yaml
Recent days: !binder search type=JournalDay "dayPeriod>=$(date -v-7d +%Y-%m-%d)" -f "dayPeriod,plan,achievements,summary" --format yaml
Flow
1. Carry-forward review
Present the source day's unfinished plan items (not in achievements). For each, ask:
- Move to target day
- Schedule for later this week → specify which day
- Drop
Flag zombie tasks — anything that's been unfinished for 3+ consecutive days:
"This has been on your list since [date]. Commit to a specific day or kill it."
Force a decision. No silent rolling.
2. Week plan pull
Show items from the week plan that haven't appeared on recent day plans. Ask: "Any of these for [target day date]?"
3. Additional tasks
"Anything else? Appointments, errands, personal?"
Output
Use binder update to write all agreed changes in one step — do not skip any:
- Target day plan — update the target day entry (key from context) with agreed items as a single multi-line string. Can include context paragraphs (e.g. weekend notes, energy expectations) followed by a plain bullet list — no checkboxes.
- Rescheduled items — for every item moved to a future day during carry-forward review, read that day's existing plan first, then
binder update <that-day-key>to add it. Do this immediately, not as an afterthought.
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.
- 6d ago First seen · 57 lines · 17 tokens per session scan A 404d420dd8ed
day-next-plan is a skill published in the GitHub repository mpazik/Binder (40 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 654 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-30.
Other skills, from other repositories
engraphis-memory
Give the agent durable, scoped, explainable memory across sessions and repositories through the Engraphis MCP tools. Use when you learn a convention, decision, bug cause/fix, or user preference worth keeping; when prior context would help before you answer or act (to avoid re-asking or re-deriving); when asked "why is…
encyclopedia-writing
Encyclopedic neutral-reference writing craft — NPOV (attribute facts not opinions, due weight, neutral faction labels, verdict restraint), summary style and Coatrack avoidance, wikilink conventions (link density, first-mention, slug alias, abbreviation glossing). Use when writing or reviewing a neutral…
guideline-writing
Guideline-authoring craft for instruction SoTs (.claude/ guides, CLAUDE.md, plan files) — operative rules vs recital, MUST/SHOULD/MAY force tiers, pruning, bloat control, blind review protocol, deliberation-narrative ban. Use when writing, editing, or reviewing an agent instruction file, policy, runbook, command SoT…
journalism-writing
Journalism and argumentation writing craft — inverted pyramid, lede, nut graph, kicker, explainer framing, PAGE frames, Toulmin argument (claim/rebuttal/qualifier), Hegelian dialectic, BBC due impartiality. Use when writing or reviewing news/explainer pieces, landscape overviews, or issue analyses that fairly…
scholarly-citation
Verifiable-attribution and citation-discipline craft — atomic claim decomposition, evidence grading (primary/analysis/forecast tiers), claimant attribution, citation typing (cites/references/contradicts/defines), source anchoring (Xanadu). Use when writing or reviewing a reference or synthesis page that attributes and…
consulting-writing
Management-consulting writing craft — McKinsey SCR (Situation·Complication·Resolution), Minto Pyramid/MECE, BCG bold-bullet executive summary, so-what upfront, numeric precision, Forrester Landscape. Use when writing or reviewing an executive summary for decision-makers or a roll-up/landscape overview, or when a…