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 AdrianV101/obsidian-pkm-plugin --skill tackle-taskgit clone --depth 1 https://github.com/AdrianV101/obsidian-pkm-pluginWrote 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/adrianv101/obsidian-pkm-plugin/tackle-task)<a href="https://agentmods.dev/skills/adrianv101/obsidian-pkm-plugin/tackle-task"><img src="https://agentmods.dev/badge/skills/adrianv101/obsidian-pkm-plugin/tackle-task.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.00031 | $0.00873 |
| Opus 5 | $0.00015 | $0.00436 |
| Sonnet 5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
tackle-task 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 7d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tackle Task
Open a task, understand what it requires, execute it at the right level of rigor, and close it properly.
Step 1: Resolve the task
From the user's message, extract either a task path or a task title/name.
- Path given:
vault_read(path)directly - Title/name given: issue two queries and match by H1 title or basename:
If multiple tasks match, show candidates and ask the user to pick. Fall back tovault_query({ type: "task", status: "pending" }) vault_query({ type: "task", status: "active" })vault_search(title)if queries return nothing.
If the task can't be found, tell the user and stop.
Once found, mark it active: vault_update_frontmatter({ path, fields: { status: "active" } }).
Step 2: Read and assess
Read the full task note. Extract:
- Title and description
- Acceptance criteria (if present — key signal for scope clarity)
- Priority and due date
- Project context
Step 3: Complexity check
Classify into one tier using these signals. This should take seconds, not minutes — trust your first read.
| Tier | Signals | Route to |
|---|---|---|
| Trivial | Single concern, obvious change, clear AC, file/location already known | Step 5 directly (skip Step 4) |
| Standard | Multi-file change, small feature or bugfix, scope is clear but needs a plan | Step 4 → Explore → Plan → Code → Commit |
| Significant | New feature, architectural impact, vague requirements, multiple unknowns | Step 4 → superpowers:brainstorming → full pipeline |
When uncertain between tiers, go one tier up. A few extra minutes of planning is almost always cheaper than an incomplete or wrong implementation.
Complexity keywords that push up a tier: "design", "architecture", "integrate", "migrate", "refactor across", "not sure how", any missing acceptance criteria.
Step 4: Explore context (Standard and Significant only)
vault_neighborhood(task_path, depth: 2)— find related ADRs, research notes, prior decisions linked from the taskvault_activity({ path: project_folder, limit: 20 })— see recent related work to avoid duplicating effort- Read any directly relevant linked notes (ADRs, research) before proceeding
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.
- 7d ago First seen · 75 lines · 31 tokens per session scan A 028a45c1f41c
tackle-task is a skill published in the GitHub repository AdrianV101/obsidian-pkm-plugin (13 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 873 once invoked, about $0.0002 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 skills, from other repositories
project-sync
On-demand AI-powered sync of a project's repo state into the brain vault. Reads live git/GitHub/Jira data, updates the project status doc, and makes targeted edits to relevant brain docs where content is clearly stale. Triggered by "/project-sync [name]", "sync [project]", "what's the current state of [project]".
log-decision
Log cross-cutting business/product/hiring/vendor decisions to decisions/ directory with context and alternatives.
owd-albatross
Connect, initialize, resume, or coordinate MDevolved Projects from Albatross using its agent.config.json stdio MCP surface, a pinned OAuth bridge, qualified tool names, workspace prompt continuity, path forks, resets, and independently attributable participant identities. Use when a repository runs Albatross, contains…
owd-eve
Connect, initialize, resume, or coordinate MDevolved Projects from an Eve agent using Eve's standard remote MCP connection, user-scoped Vercel Connect OAuth, qualified tool names, durable Project continuity, and independently attributable agent identities. Use when an Eve repository has agent/connections, when adding…
mdevolved-eve
Connect or resume an Eve agent with MDevolved through a user-scoped remote MCP connection while preserving Eve runtime identity and MDevolved Project continuity.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.