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 lexbritvin/obsidian-skills-pack --skill obsidian-tasks-cligit clone --depth 1 https://github.com/lexbritvin/obsidian-skills-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/skills/lexbritvin/obsidian-skills-pack/obsidian-tasks-cli)<a href="https://agentmods.dev/skills/lexbritvin/obsidian-skills-pack/obsidian-tasks-cli"><img src="https://agentmods.dev/badge/skills/lexbritvin/obsidian-skills-pack/obsidian-tasks-cli/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/lexbritvin/obsidian-skills-pack/obsidian-tasks-cli"><img src="https://agentmods.dev/badge/skills/lexbritvin/obsidian-skills-pack/obsidian-tasks-cli.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.00090 | $0.03156 |
| Opus 5 | $0.00045 | $0.01578 |
| Sonnet 5 | $0.00018 | $0.00631 |
| Haiku 4.5 | $0.00009 | $0.00316 |
Grade A, and why
obsidian-tasks-cli 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 3d 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.
Managing Tasks via CLI
Use the obsidian CLI to read and update tasks. Obsidian must be running.
Start with simple CLI commands. Only use obsidian eval when you need filtering that CLI flags can't express (by priority, dates, tags, or custom logic).
Listing Tasks
obsidian tasks todo # all incomplete tasks
obsidian tasks done # completed tasks
obsidian tasks todo format=json # JSON output for parsing
obsidian tasks verbose # grouped by file
obsidian tasks todo total # count only
obsidian tasks todo path="Projects" # filter by folder
obsidian tasks todo file="Shopping" # filter by file name
obsidian tasks daily todo # tasks from daily note
JSON output shape:
[
{
"status": " ",
"text": "- [ ] Buy groceries 📅 2025-04-10",
"file": "Projects/Shopping.md",
"line": "12"
}
]
Status characters: " " = TODO, "/" = IN_PROGRESS, "x" = DONE, "-" = CANCELLED.
Updating Tasks
obsidian task path="note.md" line=12 toggle # toggle status
obsidian task path="note.md" line=12 done # mark done
obsidian task path="note.md" line=12 todo # mark todo
obsidian task path="note.md" line=12 status="/" # set in-progress
To add a new task to a file:
obsidian append path="note.md" content="- [ ] New task 📅 2025-04-10"
append writes whatever text you give it verbatim — match the vault's Task Format setting (Settings → Tasks → Task Format). If it's set to Dataview format, write [due:: 2025-04-10] instead of 📅 2025-04-10 (see obsidian-tasks-syntax for the full field mapping). Check taskFormat in the Tasks plugin's data.json ("emoji" or "dataview") if unsure.
Advanced Queries via Plugin API
For filtering by priority, dates, tags, or any combination — use obsidian eval to access the Tasks plugin cache. The cache holds all parsed task objects with rich queryable properties.
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.
- 3d ago Changed · +2 lines abb9b415024d
- 10d ago First seen · 253 lines · 90 tokens per session scan A 34783fa1e16f
obsidian-tasks-cli is a skill published in the GitHub repository lexbritvin/obsidian-skills-pack (2 stars, last pushed 5d ago), licensed MIT. It adds 90 tokens to every session and 3,156 once invoked, about $0.0005 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
gtd-evening
A guided evening routine for a GTD task system, where GTD means sorting work into clear next actions, waiting items, and projects. It reviews the day, records results, and tidies unfinished work.
patent-docket
A workflow coordinator for patent case files, from an inventor's technical disclosure to patent application documents. A patent docket is the tracked record of a patent matter, including its stage, questions, drafts, and handoffs.
project-flow-ops
Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
tasks
Create or update the live task dashboard (TASKS.md) in Obsidian. Use when the user wants to view or regenerate the task dashboard — 'show my tasks', 'update TASKS.md', 'open task view'. Do NOT use for: the vault portal/map (use moc), capturing new tasks (add them inside project notes directly), or daily briefing (use…
issue-match
Measure a target repository's queue and find a live open issue the contribution would close, before opening a pull request there. Reports how many PRs are open, how many of the last N closed ones were actually merged, and which issue to attach to, because a cold PR into a dead queue is a wasted artifact. Triggers…
goal-tracking
Track progress toward 3-year, yearly, monthly, and weekly goals. Calculate completion percentages, surface stalled goals, connect daily tasks to objectives. Use for goal reviews and progress tracking.