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 aplaceforallmystuff/daily-patterns-pack --skill log-to-dailygit clone --depth 1 https://github.com/aplaceforallmystuff/daily-patterns-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/aplaceforallmystuff/daily-patterns-pack/log-to-daily)<a href="https://agentmods.dev/skills/aplaceforallmystuff/daily-patterns-pack/log-to-daily"><img src="https://agentmods.dev/badge/skills/aplaceforallmystuff/daily-patterns-pack/log-to-daily/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/aplaceforallmystuff/daily-patterns-pack/log-to-daily"><img src="https://agentmods.dev/badge/skills/aplaceforallmystuff/daily-patterns-pack/log-to-daily.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 3 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00029 | $0.00995 |
| Opus 5 | $0.00015 | $0.00498 |
| Sonnet 5 | $0.00006 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
log-to-daily 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<when_to_use>
- End of a work session (before closing Claude)
- After completing a significant piece of work
- When important decisions were made that should be recorded
- When the user explicitly requests logging
- Mid-session when switching contexts
NOT needed when:
- Just chatting without meaningful work output
- Quick questions with no decisions or outcomes </when_to_use>
<daily_note_location>
Default path pattern: 00 Daily/YYYY/YYYYMMDD.md
Common alternatives:
daily/YYYY-MM-DD.mdDaily Notes/YYYY/YYYYMMDD.mdjournals/YYYY/MM/DD.md
If the default doesn't exist, check CLAUDE.md for the user's daily note configuration, or ask. </daily_note_location>
<log_format>
---
## Session Log - [TIME]
**Focus:** [1-2 sentence summary of main work]
### Completed
- [Concrete outcome 1]
- [Concrete outcome 2]
### Decisions Made
| Decision | Rationale |
|----------|-----------|
| [Decision] | [Why] |
### Files Created/Modified
- [[filename]] - [what/why]
### Next Steps
- [ ] [Follow-up task if any]
---
</log_format>
-
Locate today's daily note
- Check default path:
00 Daily/YYYY/YYYYMMDD.md - Create if it doesn't exist (use minimal frontmatter)
- If path unclear, ask user
- Check default path:
-
Append the session log using the format above
- Use
---separator before the log - Include timestamp (user's local time)
- Be specific about outcomes, not activities
- Link to created files with
[[wikilinks]]
- Use
-
Confirm what was logged
<quality_guidelines> Good entries:
- "Created YouTube analytics inbox item with 3 integration options"
- "Refactored authentication to use JWT instead of sessions"
- "Decision: Use Postgres over SQLite (need concurrent writes)"
Bad entries:
- "Worked on stuff"
- "Had a conversation about the project"
- "Did some research"
Be specific. Capture what was DONE, not what was discussed.
Why this matters: Vault-analyst reads these logs to find patterns. Vague entries = weak pattern detection. Specific entries = actionable automation recommendations. </quality_guidelines>
<example_output>
Session Log - 2:45 PM
Focus: Local LLM integration for cost optimization
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 · 147 lines · 29 tokens per session scan A c1c72584048c
log-to-daily is a skill published in the GitHub repository aplaceforallmystuff/daily-patterns-pack (40 stars, last pushed 23d ago), licensed MIT. It adds 29 tokens to every session and 995 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
c-obsidian
Obsidian vault as persistent memory — daily notes, session logs, knowledge capture, and search across your entire vault.
wiki-switch
Switch between multiple Obsidian wiki vault profiles. Use this skill when the user says "/wiki-switch NAME", "switch to my work wiki", "switch vault", "change wiki", "which wiki am I on", "list my wikis", "show my vaults", "create a new vault config", or "add a new wiki profile". The skill manages named config files…
knowledge-base-management
A lifecycle system for managing an Obsidian knowledge base, which is a folder of linked notes. It organizes raw material, AI-maintained wiki pages, and generated views into separate layers.
obsidian
Use the official Obsidian CLI (v1.12+) to manage vaults, notes, daily notes, search, tasks, tags, properties, links, templates, sync, publish, and workspaces. Use when the user mentions Obsidian, vaults, notes, or wants to automate note-taking and knowledge base workflows.
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…