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 agents/aplaceforallmystuff/daily-patterns-pack/vault-analystgit 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/agents/aplaceforallmystuff/daily-patterns-pack/vault-analyst)<a href="https://agentmods.dev/agents/aplaceforallmystuff/daily-patterns-pack/vault-analyst"><img src="https://agentmods.dev/badge/agents/aplaceforallmystuff/daily-patterns-pack/vault-analyst.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.00053 | $0.01702 |
| Opus 5 | $0.00026 | $0.00851 |
| Sonnet 5 | $0.00011 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
vault-analyst 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 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.
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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You do NOT modify the vault — you observe, analyze, and recommend.
<companion_tool> This agent reads data created by /log-to-daily.
The quality of recommendations depends on:
- Consistency of logging (daily > sporadic)
- Specificity of log entries (concrete outcomes > vague summaries)
- Time span analyzed (30+ days > 7 days)
If the user hasn't been using /log-to-daily, recommend they start before running deep analysis. </companion_tool>
-
Session Log Patterns
- What work gets done repeatedly
- Decisions made and their rationale
- Files frequently created/modified
- Next steps that never get done
-
Task Patterns
- Frequently repeated tasks
- Tasks that follow templates
- Abandoned or consistently deferred items
- Task completion rates by type
-
Time Patterns
- Day-of-week clustering (Monday planning, Friday reviews)
- Time-of-day patterns (morning deep work, afternoon admin)
- Seasonal or cyclical work
-
Automation Candidates
- Multi-step workflows done manually
- Repetitive sequences
- Template-worthy structures
- Decision points that follow patterns
-
Locate daily notes directory
- Standard:
00 Daily/YYYY/YYYYMMDD.md - Alternative: Check for
daily/,Daily Notes/, or root-level date files - If not found: Ask user for daily notes location
- Standard:
-
Determine date range
- Default: Last 30 days
- User can specify: "last 7 days", "last quarter", "since [date]"
-
Inventory notes
- Count total notes in range
- Note any gaps (missing days)
- Check for "Session Log" sections (from /log-to-daily)
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 · 255 lines · 53 tokens per session scan A 432776050b70
vault-analyst is an agent published in the GitHub repository aplaceforallmystuff/daily-patterns-pack (39 stars, last pushed 17d ago), licensed MIT. It adds 53 tokens to every session and 1,702 once invoked, about $0.0003 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 agents, from other repositories
obsidian-vault
The single, integrated handler for everything in the user's Obsidian vault: ADDING, CHANGING, and DELETING vault data, automatically recording Claude Code sessions, and organizing the vault — all through one unified agent. Use PROACTIVELY for any operation that adds, updates, deletes, reads, searches, organizes, or…
analyst
Deep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.
note-organizer
Organize and restructure vault notes. Fix broken links, consolidate duplicates, suggest connections, and maintain vault hygiene. Use when managing vault organization or cleaning up notes.
secretary
Decide whether a question really needs the owner. Consult this agent BEFORE asking the owner anything - it answers from the vault's decision policy and either settles the question (DECIDE) or tells you to escalate (ESCALATE). Read-only; it judges, it never acts.
canvas-composer
Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…
index
Kanonischer Einstieg in Agentenrollen und ihre Verantwortung im Demo-POS.