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 AtlasOmnia/hermes-custom-pack --skill daily-note-wrapupgit clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-packWrote 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/atlasomnia/hermes-custom-pack/daily-note-wrapup)<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/daily-note-wrapup"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/daily-note-wrapup/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/atlasomnia/hermes-custom-pack/daily-note-wrapup"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/daily-note-wrapup.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.00027 | $0.01000 |
| Opus 5 | $0.00014 | $0.00500 |
| Sonnet 5 | $0.00005 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
daily-note-wrapup 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 10d 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.
This is a copy
100% identical to daily-note-wrapup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Note Wrap-Up Workflow
Use this skill for evening wrap-up work that creates tomorrow's daily note and updates the monthly daily-note index.
Core rules
- Treat the requested daily-note structure as a contract; preserve section order exactly.
- Carry forward incomplete work into tomorrow's note.
- On weekends, omit any work-specific section (for example
### [Work]) entirely rather than leaving an empty heading or placeholder bullet. - If a section has nothing to place, follow the user's exact omission rule for that section rather than inventing filler text.
- Keep today's note untouched; only create or update tomorrow's note and the monthly index.
- Serialize all mutations to the same file. Never launch parallel patches against one note or monthly index; combine related edits into one cohesive patch when practical, or patch sequentially with a read-back between changes.
Structure gotchas
- The daily note template is not a generic form: match the user's requested headings and ordering exactly, including weekend-only omissions.
- Do not leave a blank
### [Work]heading on weekends; remove the section entirely. - Use
Noneonly where the requested structure explicitly asks for it (for example,Waiting / Blocked), and omit empty sections otherwise.
Recommended workflow
- Determine today's date and tomorrow's date in the relevant timezone.
- Read today's daily note and extract useful context from
## Logand## Wins. - Gather carry-forward items from incomplete work and overdue Todoist items. Treat these as independent inputs: unchecked items in today's note still carry forward even when Todoist returns no matches. Before interpreting an empty Todoist result as "nothing due," confirm that the command actually applied date/filter semantics rather than literal keyword matching; preserve the command evidence, but do not silently discard known pending work.
- Write tomorrow's daily note with the exact requested structure.
- Update the monthly index for the target month under the correct
## Weekdaysor## Weekendssection. - Read both files back from disk before reporting completion.
- If the on-disk note looks stale, reordered, or partially replaced, rewrite the whole file through a sibling temp file + atomic rename and then re-read before trusting the result.
- If the atomic replacement still snaps back after a delay, stage the intended note, then run
scripts/atomic-note-replace-verify.sh <intended-note> <target-note>. It atomically replaces the target, protects the new inode while a stale one-shot writer abandons its write, clears protection safely, and proves byte stability for 30 seconds locked plus 20 seconds unlocked. Afterward, separately validate the note's required headings/content and the monthly index.
What ships with it
1 file 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.
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.
- 10d ago First seen · 59 lines · 27 tokens per session scan A 810f5476ed9f
daily-note-wrapup is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (56 stars, last pushed 25d ago), licensed MIT. It adds 27 tokens to every session and 1,000 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to daily-note-wrapup, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
obshare-cli
Use when setting up obshare-cli 0.2.0, reviewing available commands, or choosing the right command for config, upload, permission, history, delete, and the plugin-first direct-share workflow.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
macos-storage-management
Safely reclaim local Mac storage without mistaking cloud placeholders for resident data, losing File Provider content, or flattening metadata onto an incompatible external filesystem.
vault-organization
Audit and reorganize the user's Obsidian vault. Run when asked to organize, clean up, or audit the vault structure — or to set up a sensible structure for a new/empty vault.
apple-reminders
Use remindctl to manage Apple Reminders directly from the terminal. Tasks sync across all Apple devices via iCloud.