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 mpazik/Binder --skill day-summarygit 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-summary)<a href="https://agentmods.dev/skills/mpazik/binder/day-summary"><img src="https://agentmods.dev/badge/skills/mpazik/binder/day-summary/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/mpazik/binder/day-summary"><img src="https://agentmods.dev/badge/skills/mpazik/binder/day-summary.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.00019 | $0.01493 |
| Opus 5.5 | $0.00008 | $0.00597 |
| Sonnet 5.5 | $0.00004 | $0.00299 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade B, and why
day-summary scanned grade B 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 1mo 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Don't moralize about procrastination — track patterns, don't judge them How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read the day's journal entry and close it out in two rounds: first discuss, then score and write.
Context
Offset controls direction: default (0) = today, negative = past day (e.g. -1 for yesterday).
Target day = the day being summarized (offset $0). Always read its date from the entry below — never assume it's "today."
Target day entry (we are summarizing this — created if missing): !O=$0; binder read $(bun scripts/journal.ts d ${O:-0} --key) --format yaml
Week context: !O=$0; binder read $(bun scripts/journal.ts w ${O:-0} --key) -f "weekPeriod,goal,plan,achievements" --format yaml
Extra context: Calendar events, activity dump, and health data are injected automatically by the data-sync extension. Use them if present. Activity dump is background context — not every commit or session is an achievement.
Recent days: !binder search type=JournalDay "dayPeriod>=$(date -v-7d +%Y-%m-%d)" -f "dayPeriod,plan,achievements,summary,moodScore,sleepScore,foodScore,workScore,fitnessScore,totalScore" --format yaml
First message — Reflect on the day
After reading the entry, deliver one message. Use plain text throughout — no blockquotes.
1. Day summary
Brief bullet points of what happened based on the log and plan. Cover what got done, what didn't, and anything notable.
Note: log entries may be added retroactively — don't infer energy flow or timing patterns from timestamps alone. Ask if the timeline is unclear.
2. Reflection
Offer a short inferred read on the day — energy, momentum, patterns vs recent days. Honest, not preachy.
3. What's missing?
Numbered list. Call out gaps: things the log doesn't cover, plan items with no mention, anything that feels incomplete. Gaps may mean "not logged yet" rather than "didn't happen" — ask "anything not captured yet?" rather than assuming omission.
4. How was it?
Ask how the day felt overall. One or two targeted questions if something specific stands out from the log. Not open-ended therapy — you already know most of the day.
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.
- 1mo ago First seen · 145 lines · 19 tokens per session scan B 0118ac6478ab
day-summary is a skill published in the GitHub repository mpazik/Binder (40 stars, last pushed 28d ago), licensed MIT. It adds 19 tokens to every session and 1,493 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
anyr
Use when reading, searching, creating, or updating Anytype documents (objects, spaces, types, properties, files, chats) from the command line with the configured anyr CLI, including JSON output patterns for scripting.
any-mcp
Use when an agent needs to read, search, create, edit, organize, upload, or chat with Anytype through the bounded any-mcp server. Covers safe tool selection, exact identifier chaining, optional toolsets, common PKM workflows, and the narrow anyr fallbacks for chat subscriptions and rich chat blocks.
anytype-setup
Install anyr and configure desktop or headless Anytype access. Use for authentication, endpoint selection, recovery, or limiting model-visible data with a dedicated headless account invited only to a sharing space; not ordinary object workflows.
recap
Summarize the last N agent sessions for the current project, grouped by date, with highlight observations per session. Use when the user asks "recap", "what have we been doing", "today", "this week", or wants a rollup of recent work.
handoff
Resume the most recent agent session for the current working directory, leading with any unanswered question. Use when the user says "where were we", "resume", "handoff", "pick up where I left off", or starts a session with no fresh context.
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…