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 period-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/period-next-plan)<a href="https://agentmods.dev/skills/mpazik/binder/period-next-plan"><img src="https://agentmods.dev/badge/skills/mpazik/binder/period-next-plan.svg" alt="Measured on agentmods" 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.00022 | $0.00906 |
| Opus 5 | $0.00011 | $0.00453 |
| Sonnet 5 | $0.00004 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
period-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 8d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up the goal and plan for the target period.
Context
Offset controls direction: proactive (positive or default — planning upcoming periods) or retroactive (negative — backfilling a past period's plan). Use actual period dates from entries below — do NOT assume "next" or "current."
Target period with parent and siblings (created if missing): !G=$0; O=$1; binder read $(bun scripts/journal.ts ${G:-w} ${O:-next} --key) -f "key,goal,plan,parent(key,goal,plan,children(key,goal,plan,achievements,summary,totalScore))" --format yaml
Previous period: !G=$0; O=$1; P=$([ "$O" = "next" ] || [ -z "$O" ] && echo 0 || echo $(( O - 1 ))); binder read $(bun scripts/journal.ts ${G:-w} $P --key) -f "goal,plan,achievements,events,summary,totalScore" --format yaml
Deliver one message
1. Parent context
Show the parent period's goal and plan in 3-5 lines. Frame it as: "Here's what [quarter/month/year] is about."
2. Sibling review & carry-forwards
Review the sibling periods (parent's children). For each completed sibling, briefly note what was achieved. For the most recent sibling:
- Diff plan vs achievements — list items that were planned but NOT achieved.
- Flag zombie items — anything planned in 2+ consecutive siblings but never achieved:
"This has been on the plan since [period]. Carry with commitment, or kill it."
- For each unfinished item, recommend: carry forward, defer to parent backlog, or drop.
3. Proposed goal
Suggest a goal for the new period, derived from:
- Parent period's goal and plan (what's the next logical chunk?)
- Unfinished items worth carrying from the sibling review
- Any obvious next steps
The goal should be 1-3 lines. Concrete, not aspirational fluff.
"Does this goal feel right, or would you adjust it?"
4. Proposed plan
Suggest a plan — concrete items that serve the goal:
- Week: max 6 items
- Month: max 5 items (broader strokes)
- Quarter: max 4 items (one per month roughly)
- Year: max 3-4 themes
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.
- 8d ago First seen · 86 lines · 22 tokens per session scan A 330196df29d4
period-next-plan is a skill published in the GitHub repository mpazik/Binder (40 stars, last pushed 16d ago), licensed MIT. It adds 22 tokens to every session and 906 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…
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.
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
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.
fkf-use
Use an fkf base safely: inspect health, retrieve bounded evidence, resolve URIs, traverse relations, collect sources, or serve read-only MCP. Invoke for base reads or collection.