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 igapyon/igapyon-agent-skills --skill igapyon-miku-daybookgit clone --depth 1 https://github.com/igapyon/igapyon-agent-skillsWrote 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/igapyon/igapyon-agent-skills/igapyon-miku-daybook)<a href="https://agentmods.dev/skills/igapyon/igapyon-agent-skills/igapyon-miku-daybook"><img src="https://agentmods.dev/badge/skills/igapyon/igapyon-agent-skills/igapyon-miku-daybook/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/igapyon/igapyon-agent-skills/igapyon-miku-daybook"><img src="https://agentmods.dev/badge/skills/igapyon/igapyon-agent-skills/igapyon-miku-daybook.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.00065 | $0.02263 |
| Opus 5.5 | $0.00026 | $0.00905 |
| Sonnet 5.5 | $0.00013 | $0.00453 |
| Haiku 4.5 | $0.00006 | $0.00226 |
Grade A, and why
igapyon-miku-daybook 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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
igapyon-miku-daybook
Manage the Markdown records in a daybook repository. The records are the source of truth; generated day-plans and GitHub notifications are derived views.
The task/activity recording policy draws on MIT OpenCourseWare's Guidelines for Keeping a Laboratory Notebook, a course resource for 7.16 Experimental Molecular Biology: Biotechnology II (Spring 2005). Keep a task's latest conclusion, state, and next actions with a brief history; keep dated work, trials, observations, and decision reasons in activities. This separation adapts the notebook approach to task management. See task and activity responsibilities for the editing rules.
Unless the user specifies another style, write narrative prose in daybook records in Japanese polite form (です・ます調). Bullet items may use concise plain-form sentences or noun phrases; do not force polite endings on every bullet.
Activation and boundaries
Use this skill when the user says igapyon-miku-daybook, miku-daybook, or clearly asks to add, update, list, or summarize records in the daybook repository. Also use it when the user explicitly asks to check or find existing daybook tasks related to a supplied URL. A URL alone or a request only to read or summarize it does not start task lookup. Use the Issue-intake procedure only when the user explicitly asks to import named GitHub Issue(s) into daybook. Also use it when the user explicitly asks to generate or update the daybook GitHub Actions notification workflow. Do not activate for a generic TODO request, an igapyon diary entry, an Issue inspection that does not ask for related daybook tasks, or a question about this skill itself.
This skill edits daybook records, local documentation, and an explicitly requested notification workflow. It does not automatically commit, push, create pull requests, dispatch workflows, send email, or synchronize Issues with tasks. Explicit Issue intake is a narrow exception: follow issue-import.md to prepare local records, then use the existing miku-scm comment and close workflows for the intake receipt and verified intake close. The daybook request authorizes that bounded workflow, but does not bypass miku-scm's current Issue snapshot, preflight, approval, apply, and attempt-recovery requirements. Do not post comments or close Issues for an Issue read, candidate list, ordinary daybook update, or resumed import unless the user's request covers that action.
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 129 B
- assets/daybook/.github/workflows/day-plan-notify.yml 3.8 KB
- assets/daybook/package-lock.json 668 B
- assets/daybook/package.json 187 B
- assets/daybook/scripts/day-plan.mjs 17 KB runs code
- assets/daybook/scripts/day-plan.test.mjs 19 KB runs code
- assets/daybook/scripts/generate-day-plan.mjs 1.2 KB runs code
- assets/daybook/scripts/import-issues.mjs 9.5 KB runs code
- assets/daybook/scripts/import-issues.test.mjs 4.6 KB runs code
- assets/daybook/scripts/issue-import.mjs 89 KB runs code
- assets/daybook/scripts/issue-import.test.mjs 24 KB runs code
- assets/daybook/scripts/post-day-plan.mjs 7.3 KB runs code
- assets/daybook/scripts/post-day-plan.test.mjs 8.3 KB runs code
- references/issue-import.md 22 KB
- references/notification.md 4.9 KB
- references/operations.md 21 KB
- references/records.md 9.7 KB
- references/task-date-migration.md 5.7 KB
- references/url-task-lookup.md 5.9 KB
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.
- 2d ago Changed · +7 lines · +2 tokens per session 19a11126478e
- 3d ago Changed · -1 lines a43c9ae477c7
- 11d ago Changed · +1 lines · +3 tokens per session e3fd2697cfdd
- 12d ago Changed · +2 lines d986fde67498
- 15d ago Changed · +4 lines ce49750597ce
- 22d ago Changed · +4 lines 68cf3829350a
- 26d ago Changed · +2 lines · -9 tokens per session 39880b435059
- 1mo ago First seen · 39 lines · 69 tokens per session scan A d645ff72980d
igapyon-miku-daybook is a skill published in the GitHub repository igapyon/igapyon-agent-skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 2,263 once invoked, about $0.0003 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-09-14.
Other skills, from other repositories
workflow-manager
A writing workflow tracker for chapter-based projects. It records whether each chapter is being assembled, drafted, reviewed, confirmed, polished, or archived.
dog-review-query
Query an existing hierarchical OpenWrite review-v2 artifact through dsh-dog. Use after novelreviewchapter or when inspecting six quality domains, evidence, coverage, blockers, delivery status, or the 37 legacy checks. Never rerun model review from DoG.
dog-delivery-query
Query a chapter delivery DoG graph across manuscript, review, revision application, and re-review closure. Use after writing or reviewing a chapter, after revision actions, or when the user asks whether a chapter is truly ready to deliver.
dog-import-query
Query a smart-import DoG graph after a novel has been split into chapters. Use to inspect import completeness, AI precheck errors, and pending outline/asset/canonical setup.
progress
A progress report for a writing project. It reads the project's current status, chapter details, background tasks, and unresolved story threads.
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.