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 jason-c-dev/obsidian-mcp --skill standupgit clone --depth 1 https://github.com/jason-c-dev/obsidian-mcpWrote 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/jason-c-dev/obsidian-mcp/standup)<a href="https://agentmods.dev/skills/jason-c-dev/obsidian-mcp/standup"><img src="https://agentmods.dev/badge/skills/jason-c-dev/obsidian-mcp/standup.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.1 | $0.00025 | $0.00237 |
| Opus 5 | $0.00013 | $0.00118 |
| Sonnet 5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
standup 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 6d 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
Standup Summary
Generate a standup update based on what's actually in the vault.
Steps
-
Yesterday's note — call
vault_readwithpathset to yesterday's date (e.g.,path: "2026-03-01.md"). Calculate yesterday's date. -
Today's note — call
vault_daily_read -
Outstanding tasks — call
vault_taskswithstatus: "todo" -
Recently completed tasks — call
vault_taskswithstatus: "done"
Output Format
Yesterday
- What was accomplished (from yesterday's daily note and completed tasks)
Today
- What's planned (from today's daily note and outstanding tasks)
Blockers
- Any blockers or dependencies mentioned in notes
Keep it concise — this is standup format. No fluff. If there's not enough data for a section, say "Nothing captured in vault" rather than making things up.
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.
- 6d ago First seen · 33 lines · 25 tokens per session scan A 7d45a5f67003
standup is a skill published in the GitHub repository jason-c-dev/obsidian-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 237 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.