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-startgit 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-start)<a href="https://agentmods.dev/skills/mpazik/binder/day-start"><img src="https://agentmods.dev/badge/skills/mpazik/binder/day-start/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-start"><img src="https://agentmods.dev/badge/skills/mpazik/binder/day-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.01023 |
| Opus 5.5 | $0.00006 | $0.00409 |
| Sonnet 5.5 | $0.00003 | $0.00205 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
day-start 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 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.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deliver a focused day briefing. Get me moving in under 3 minutes. This may run hours after waking — don't assume it's the first thing in the day.
Context
Offset controls direction: proactive (positive or default — briefing days ahead) or retroactive (negative — briefing a past day).
Target day = the day being briefed (offset $0). Always read its date from the entry below — never assume it's "today."
Target day entry (we are briefing 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 and health data are injected automatically by the data-sync extension. Use them if present.
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
Deliver the briefing FIRST (no questions)
Open with a short recap. Format:
Previous day: [1-2 sentence summary of what happened + key outcome. Include the highlight if one was captured — e.g. "Best part: nailed the demo."] This week: [week goal] — [progress based on achievements so far] Momentum: [streaks, positive trends, and recent achievements, e.g. "Gym 4 days straight. Work score up from 5→7. Shipped frontmatter parser yesterday."]
4 lines max. Focus on momentum and context, not rehashing failures. If the previous day was rough, acknowledge briefly and move on: "Fresh day. Here's what's ahead."
Then ask — one combined message
Propose scores from health data
If healthData contains sleep data, propose a sleep score in the briefing — don't ask about sleep. Use recent days' sleep data and scores as calibration (e.g. if 8.3h scored 8, and today is 7.0h with low deep sleep, propose 6). Show your reasoning briefly:
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 · 97 lines · 16 tokens per session scan A c7ea9f6626b7
day-start is a skill published in the GitHub repository mpazik/Binder (40 stars, last pushed 28d ago), licensed MIT. It adds 16 tokens to every session and 1,023 once invoked, about $0.0001 per session on Opus 5.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
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…