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.
git 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/plugins/aplaceforallmystuff/daily-patterns-pack/daily-patterns-pack)<a href="https://agentmods.dev/plugins/aplaceforallmystuff/daily-patterns-pack/daily-patterns-pack"><img src="https://agentmods.dev/badge/plugins/aplaceforallmystuff/daily-patterns-pack/daily-patterns-pack/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/plugins/aplaceforallmystuff/daily-patterns-pack/daily-patterns-pack"><img src="https://agentmods.dev/badge/plugins/aplaceforallmystuff/daily-patterns-pack/daily-patterns-pack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
daily-patterns-pack 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 1mo 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.
What it actually says
{
"name": "daily-patterns-pack",
"displayName": "Daily Patterns Pack",
"description": "Log Claude Code sessions to Obsidian daily notes, analyze patterns, and build automations. A feedback loop that learns how you work.",
"version": "1.0.0",
"author": {
"name": "Jim Christian",
"email": "[email protected]",
"url": "https://jimchristian.net"
},
"homepage": "https://github.com/aplaceforallmystuff/daily-patterns-pack#readme",
"repository": "https://github.com/aplaceforallmystuff/daily-patterns-pack",
"license": "MIT",
"keywords": [
"obsidian",
"daily-notes",
"productivity",
"patterns",
"automation"
]
}
What it installs
The manifest is a name and a version. 1 skill, 1 agent travel with it, and installing the plugin installs all of them — 82 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 22 lines scan A 2d4a309dbdc7
daily-patterns-pack is a plugin published in the GitHub repository aplaceforallmystuff/daily-patterns-pack (41 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
obsidian-chronicle
Auto-records Claude Code sessions as structured Obsidian notes + Daily Note entries (via the SessionEnd/PreCompact hooks and /done), and ships the obsidian-vault agent — the unified handler for all Obsidian vault work (create, edit, search, organize notes, tasks, canvases, bases). Configure with…
obsidian-wiki
Grow an Obsidian second brain with your AI agent: ingest docs, chat history and URLs into interlinked markdown, then query it with citations. Karpathy's LLM Wiki pattern as Claude Code skills.
llm-wiki
Self-maintaining LLM wiki (Karpathy pattern): recall, observe, retro, capture sources, ensure pages, lint, and ingest. 15 tools over MCP.
para-knowledge-base
Build, query, index, and audit portable PARA knowledge bases in Obsidian with privacy-safe operation telemetry.
vault-template
Personal Knowledge Management system for Obsidian with AI-powered workflows, goal tracking, and productivity coaching.
superbrain
Automatic Claude Code -> Obsidian second brain: zero-config session capture, hybrid search, autonomous recall, daily/lessons/preferences.