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/sjungling/sjungling-claude-pluginsWrote 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/commands/sjungling/sjungling-claude-plugins/add-to-daily-note)<a href="https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/add-to-daily-note"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/add-to-daily-note/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/commands/sjungling/sjungling-claude-plugins/add-to-daily-note"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/add-to-daily-note.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.00017 | $0.01251 |
| Opus 5 | $0.00009 | $0.00626 |
| Sonnet 5 | $0.00003 | $0.00250 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
add-to-daily-note 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 11d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture $ARGUMENTS into today's daily note in Obsidian.
The full CLI surface and every caveat live in the shared reference: the
technical-writer:obsidian-vault-manager skill →
references/obsidian-cli-reference.md (see the Default / active vault, Daily
notes, and iCloud vaults & sandboxing sections). Consult it if any step is unclear.
Two things that will bite you if ignored:
- Run every
obsidianCLI call with the sandbox disabled. The CLI talks to the running Obsidian app over a local socket the command sandbox blocks, so a sandboxed call hangs. - The CLI prepends a startup banner to stdout on every call ("Loading updated app
package…", installer-out-of-date, an
obsidian.mdURL). Always filter it when capturing output into a variable — the snippets below do this positionally (grep '^name',grep '\.md$').
If the capture text ($ARGUMENTS) is empty, ask the user what to capture — don't append
an empty bullet.
This command acts; it does not gate. Appending to a daily note is trivial and
reversible. Do not enter plan mode, write a plan file, or call ExitPlanMode for it —
the session's own permission prompt on the daily:append call is the only checkpoint you
need. Ask a clarifying question only for the one genuine fork below (long content), and
prefer a sensible default over asking.
Step 1 — Resolve the target vault
Default to the CLI's active vault — this is "the default vault":
VAULT=$(obsidian vault | grep '^name' | cut -f2-)
If $ARGUMENTS begins with a vault=<name> token, use that name instead and strip the
token from the summary text. Validate an override with obsidian vault "<name>"; if it
errors, show obsidian vaults and stop (name typo).
Step 2 — Resolve today's daily note
DAILY=$(obsidian "vault=$VAULT" daily:path | grep -E '\.md$' | head -n1)
If $DAILY is empty, the vault has no Daily Notes / Periodic Notes plugin configured (or
it isn't the active vault — daily commands target the active vault). Report that and stop;
do not fabricate a path.
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.
- 11d ago First seen · 110 lines · 0 tokens per session scan A e01dd1db5f9f
add-to-daily-note is a command published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 28d ago), licensed MIT. It adds 17 tokens to every session and 1,251 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 commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.