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 jqaisystems/jqai-ai-skills --skill obsidian-daily-notegit clone --depth 1 https://github.com/jqaisystems/jqai-ai-skillsWrote 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/jqaisystems/jqai-ai-skills/obsidian-daily-note)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/obsidian-daily-note"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/obsidian-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/skills/jqaisystems/jqai-ai-skills/obsidian-daily-note"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/obsidian-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.00079 | $0.00634 |
| Opus 5 | $0.00039 | $0.00317 |
| Sonnet 5 | $0.00016 | $0.00127 |
| Haiku 4.5 | $0.00008 | $0.00063 |
Grade A, and why
obsidian-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 12d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Daily Note
Append a thought, log entry, or reminder to today's daily note in an Obsidian vault without leaving the terminal. The note is created if it does not exist, and existing content is never overwritten.
Step 0: Find the vault (once)
Resolve the configuration in this order:
- A
daily-note.config.mdfile in the current project or its parents, with:
VAULT_PATH Absolute path to the Obsidian vault root
NOTES_FOLDER Folder for daily notes relative to the vault, e.g. "Daily" or "_Notes"
DATE_FORMAT File name date format, default YYYY-MM-DD
- If no config file exists: check whether the current directory (or a parent) contains a
.obsidianfolder. If so, that is the vault; read.obsidian/daily-notes.jsonfor the folder and format if present. - Otherwise ask the user for vault path and notes folder, then offer to save the answers to
daily-note.config.mdfor next time.
Never guess a vault path. Writing notes into the wrong directory is worse than asking once.
Step 1: Build the file path
- Get today's date from the current-date context (never from training data).
- Build the path:
VAULT_PATH/NOTES_FOLDER/<date in DATE_FORMAT>.md
Step 2: Write
- If the file does not exist: create it with a
# <date>heading, then the new section. - If the file already exists: read it first, then append the new section at the end. Never overwrite or reorder existing content.
Section format:
## <section title>
<the user's text>
Title rules:
- If the user separates a title from the body (for example with a
|), use their title. - If the text starts with an obvious label ("Meeting with X:", "Reminder:"), use that.
- Otherwise use
Note.
Keep the user's text as written. Light cleanup (trim whitespace, fix an obvious typo the user flags) is fine; rewriting their words is not.
Step 3: Confirm
Report what was written and the full file path, and whether the note was created or appended to.
Rules
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.
- 12d ago First seen · 62 lines · 79 tokens per session scan A 8bce361dd6d4
obsidian-daily-note is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 634 once invoked, about $0.0004 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-31.
Other skills, from other repositories
session-manager
A fallback skill for recording development sessions and restoring project context from an Obsidian vault, a folder of linked notes. It handles explicit resume, handoff, status, and end-of-session requests when automatic capture is unavailable.
sfl
Save For Later: checkpoint this window so a fresh session (or /nil) can resume it later. Use when the user types /sfl, "save for later", or "checkpoint this window". Writes a live per-window entry under /.claude/sfl/ (plus an optional durable note in the user's own memory system), then shows the green Saved-for-Later…
today
Morning heartbeat — staleness checks, deadline surfacing, and memory curation for your workspace state. Run at the start of each day or after a 12+ hour gap.
update
Mid-session checkpoint — append progress to today's session log and update state files if a priority shifted, without ending the session.
shipkit-work-memory
Log session progress and save resume state. Infers from conversation and git. Triggers: 'log progress', 'session summary', 'checkpoint', 'save progress', 'end session'.
session-update
Use when the user says "update session", "log progress", "checkpoint session", or invokes /session-update — especially before /clear or handoff.