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 arch3rPro/ark-space --skill obsidian-kanbangit clone --depth 1 https://github.com/arch3rPro/ark-spaceWrote 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/arch3rpro/ark-space/obsidian-kanban)<a href="https://agentmods.dev/skills/arch3rpro/ark-space/obsidian-kanban"><img src="https://agentmods.dev/badge/skills/arch3rpro/ark-space/obsidian-kanban/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/arch3rpro/ark-space/obsidian-kanban"><img src="https://agentmods.dev/badge/skills/arch3rpro/ark-space/obsidian-kanban.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.00100 | $0.01821 |
| Opus 5 | $0.00050 | $0.00911 |
| Sonnet 5 | $0.00020 | $0.00364 |
| Haiku 4.5 | $0.00010 | $0.00182 |
Grade A, and why
obsidian-kanban 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 9d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Kanban
Overview
Create and maintain Obsidian Kanban boards as durable task systems rather than one-off lists. Default to a mixed task model: capture simple work as lightweight cards, then upgrade complex work into linked notes when the task needs more context, history, or attachments. For GTD boards, prefer trusted list semantics over generic priority queues: the board should clarify what the task is, where it belongs, and what the next visible action is.
Workflow
- Identify the target board file and read the current structure before editing.
- Preserve the existing board frontmatter, list names, archive separator, and
kanban:settingsblock unless the user asks for structural changes. - Decide whether each task should remain a lightweight card or be upgraded to a linked note.
- Apply the task conventions below consistently so future edits remain predictable.
- Validate the board after editing: headings still align with lists, cards still sit under the intended list, indentation remains valid Markdown, and the settings block is still intact.
Task Model
Lightweight card
Use a lightweight card when the task is actionable without extra documentation. Prefer this shape:
- [ ] Prepare quarterly planning draft @{2026-05-02} @@{09:00} #planning #work
- [ ] Pull current metrics
- [ ] Draft agenda
Use this model for fast capture, inbox triage, and routine task maintenance.
Treat priority as optional rather than foundational. In GTD boards, contexts and list placement should carry most of the organizational load.
Do not invent tags: or due: pseudo-fields. Prefer inline hashtags and the board's configured date/time triggers, which default to @{date} and @@{time}.
If the user wants visible priority that does not live in the title, do not fake it with extra card-body lines. The plugin renders those as ordinary body text. Upgrade the task to a linked note and surface priority through linked page metadata instead.
What ships with it
4 files 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.
- 9d ago First seen · 160 lines · 100 tokens per session scan A 0c78a9ee39d3
obsidian-kanban is a skill published in the GitHub repository arch3rPro/ark-space (2 stars, last pushed 14d ago), licensed MIT. It adds 100 tokens to every session and 1,821 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
dynamo-jira-ticket
Create structured Jira tickets for DynamoDS projects from bug reports, failing tests, or feature requests. Use this skill whenever writing a Jira ticket, triaging a bug, turning a vague issue into an actionable ticket, or writing acceptance criteria. Also use when the user mentions "file a ticket", "write a bug…
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…