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/period-updatenpx skills add mpazik/Binder --skill period-updategit 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-update)<a href="https://agentmods.dev/skills/mpazik/binder/period-update"><img src="https://agentmods.dev/badge/skills/mpazik/binder/period-update.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 | $0.00021 | $0.01134 |
| Opus 5 | $0.00010 | $0.00567 |
| Sonnet 5 | $0.00004 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade B, and why
period-update 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 5d 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.
- Never moralize. Never manufacture urgency. How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mid-period check-in. The period is live — things have happened, things have changed. This is a space to adjust the plan, reflect on direction, or surface something that's been building. Could be a quick tweak or a real conversation. Read the room.
Context
Target period with children so far (created if missing):
!G=$0; O=$1; binder read $(bun scripts/journal.ts ${G:-w} ${O:-0} --key) -f "key,goal,plan,achievements,events,learnings,children(key,goal,plan,achievements,events,learnings,summary,totalScore)" --format yaml
Parent context:
!G=$0; O=$1; binder read $(bun scripts/journal.ts ${G:-w} ${O:-0} --key) -f "parent(key,goal,plan,achievements,events,learnings)" --format yaml
Previous period: !G=$0; O=$1; binder read $(bun scripts/journal.ts ${G:-w} $(( ${O:-0} - 1 )) --key) -f "goal,plan,achievements,events,learnings,summary,totalScore" --format yaml
Open with a brief pulse (one message, short)
Read the period's plan, goal, current learnings, and children completed so far. Deliver a compact snapshot:
- Progress: which plan items have seen real movement (from children's achievements/summaries)
- Stalled: which plan items have had no activity
- Learning signal: one pattern that is becoming clear from current activity
- Parent thread: one line connecting this to the parent period's goal — are we on track at the larger scale?
If something stands out — a pattern, drift from the goal, unexpected momentum — name it in one honest line.
Then open the floor:
"What's changed? Anything to add, drop, or rethink?"
That's it. Don't pre-fill a structured overhaul. Don't ask multiple questions. Just open space.
Then listen
I might bring:
- New items that came up and need to go on the plan
- Items I forgot when planning that should have been there
- Items that are effectively done and should be noted
- Unexpected events worth capturing now
- A shift in priorities — something matters more or less than before
- A broader reflection on whether the goal still makes sense
- A fresh learning from recent activity that should be captured now
- Frustration about pace, focus, or direction
- Something unrelated to the plan
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.
- 5d ago First seen · 95 lines · 21 tokens per session scan B 6be7ff33dffb
period-update is a skill published in the GitHub repository mpazik/Binder (40 stars, last pushed 13d ago), licensed MIT. It adds 21 tokens to every session and 1,134 once invoked, about $0.0001 per session on Opus 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
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…