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-syntaxgit 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-syntax)<a href="https://agentmods.dev/skills/lexbritvin/obsidian-skills-pack/obsidian-tasks-syntax"><img src="https://agentmods.dev/badge/skills/lexbritvin/obsidian-skills-pack/obsidian-tasks-syntax/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-syntax"><img src="https://agentmods.dev/badge/skills/lexbritvin/obsidian-skills-pack/obsidian-tasks-syntax.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.00136 | $0.01619 |
| Opus 5 | $0.00068 | $0.00809 |
| Sonnet 5 | $0.00027 | $0.00324 |
| Haiku 4.5 | $0.00014 | $0.00162 |
Grade A, and why
obsidian-tasks-syntax 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 5d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Tasks
Task Format Setting
The Tasks plugin has two mutually exclusive ways to write metadata on a task line, chosen in Settings → Tasks → Task Format:
- Tasks Emoji Format (default) — emoji signifiers, positional. Covered below.
- Dataview Format — inline fields (
[key:: value]), read by both Tasks and the Dataview plugin.
Check which one a vault uses before writing a task line — check taskFormat in the Tasks plugin's data.json ("emoji" or "dataview"), or ask the user. Writing emoji signifiers into a vault set to Dataview format (or vice versa) means Tasks won't parse the metadata at all.
Task Line Format — Tasks Emoji Format
- [ ] Task description 🔼 🔁 every week 🛫 2025-01-01 ⏳ 2025-01-05 📅 2025-01-10
Order matters: description first, then priority, then recurrence, then dates. The Tasks plugin parses emoji signifiers by position — putting them out of order can cause misreads. Dates are always YYYY-MM-DD — natural language like "tomorrow" is not recognized on task lines (it only works in query blocks).
Task Line Format — Dataview Format
- [ ] Task description [priority:: medium] [repeat:: every week] [start:: 2025-01-01] [scheduled:: 2025-01-05] [due:: 2025-01-10]
Fields are matched by name, not position — order does not matter. Each field is its own [key:: value] bracket; don't combine several keys inside one bracket. Dates are still always YYYY-MM-DD.
Emoji → Dataview field name:
| Emoji | Dataview field | Note |
|---|---|---|
| 📅 due date | due |
|
| ⏳ scheduled date | scheduled |
|
| 🛫 start date | start |
|
| ➕ created date | created |
|
| ✅ done date | completion |
not done |
| ❌ cancelled date | cancelled |
|
| 🔺⏫🔼🔽⏬ priority | priority |
values: highest, high, medium, low, lowest (omit for Normal) |
| 🔁 recurrence | repeat |
not recurrence; rule text unchanged (every week, etc.) |
| 🆔 id | id |
|
| ⛔ dependsOn | dependsOn |
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.
- 5d ago Changed · +34 lines · +22 tokens per session 31fc7329d145
- 12d ago First seen · 88 lines · 114 tokens per session scan A 5e9b2ca1d6ae
obsidian-tasks-syntax is a skill published in the GitHub repository lexbritvin/obsidian-skills-pack (2 stars, last pushed 7d ago), licensed MIT. It adds 136 tokens to every session and 1,619 once invoked, about $0.0007 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
obsidian
Obsidian vault management — create notes, backlinks, tags, and Dataview queries via file operations.
obsidian
Organize Obsidian vaults with Markdown, URI links, Templater, Dataview, and local plugin workflows.
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.
gtd-alignment
A monthly goal-checking and coaching routine based on the user's stated strategy, values, and personal patterns. It compares time spent and actions taken with the goals the user says matter most.
gtd-inbox
A guided process for emptying a GTD inbox, where an inbox is a temporary holding place for uncategorized tasks and ideas. It examines each item and helps decide whether it belongs in actions, projects, waiting items, someday items, areas, or reference notes.
gtd-review
A guided weekly review for a GTD system, where GTD is a method for keeping tasks, projects, waiting items, and reference material organized. It prepares a review note from recent work, journal entries, and, when available, calendar events.