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 pariyar07/ariadne --skill workstream-trackinggit clone --depth 1 https://github.com/pariyar07/ariadneWrote 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/pariyar07/ariadne/workstream-tracking)<a href="https://agentmods.dev/skills/pariyar07/ariadne/workstream-tracking"><img src="https://agentmods.dev/badge/skills/pariyar07/ariadne/workstream-tracking/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/pariyar07/ariadne/workstream-tracking"><img src="https://agentmods.dev/badge/skills/pariyar07/ariadne/workstream-tracking.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.00050 | $0.01346 |
| Opus 5.5 | $0.00020 | $0.00538 |
| Sonnet 5.5 | $0.00010 | $0.00269 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
ariadne:workstream-tracking 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 1mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ariadne Workstream Tracking
Use this skill when a user wants a visible work board, implementation board, evaluation board, roadmap board, QA board, or dashboard for an Obsidian vault scope.
This skill creates and improves Markdown-backed workstream state. Kanban and Dataview are view plugins; the durable source of truth remains Markdown tasks, links, and metadata.
Plugin Requirements
Call out plugin requirements before creating plugin-specific views:
- Obsidian Kanban community plugin: required for drag-and-drop board rendering.
- Obsidian Dataview community plugin: required for dynamic dashboard query rendering.
Do not block the workflow when plugins are missing or unknown. The files still remain readable Markdown. Tell the user that visual Kanban or Dataview rendering needs the relevant plugin enabled in Obsidian.
Start
- Read the target scope hub, usually
00 Index.mdor00 ... Index.md. - Read the nearest
AGENTS.mdorCLAUDE.md. - Read
Agent/00 Agent Navigation.mdandAgent/Task Routing Matrix.mdwhen present. - Inspect existing
Kanban/,Dashboards/,Bases/, and relevant roadmap or implementation notes. - Decide whether the task is create, audit, improve, or dashboard-only.
For create, update, file, or add-tracking requests in a multi-scope vault, require a current-turn explicit target before editing. A target is explicit only when the current prompt names a scope, domain, customer, project, or workstream, or the user confirms one after the agent asks. Search hits may identify likely boards, but a single likely match, existing matching cards, prior conversation, current working directory, or active skills are not confirmation. Show the likely target with a short reason and ask before writing.
Use ariadne:navigation when the board requires broader scope routing or structural navigation changes.
Board Creation
Create Kanban/<Board Name>.md for recurring workstream state. Use assets/templates/Workstream Tracking Board.md as the starting pattern.
What ships with it
5 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.
- 1mo ago First seen · 127 lines · 50 tokens per session scan A f34a6db3787d
ariadne:workstream-tracking is a skill published in the GitHub repository pariyar07/ariadne (21 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 1,346 once invoked, about $0.0002 per session on Opus 5.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-flow-ops
Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
contrib-watch
Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.
peer-onboard
A procedure for bringing an outside lead or peer into a shared working setup, including their contact space, records, previous conversations, and ongoing session.
retro-lost
Run a retrospective for an abandoned agent session (untouched for over 24 hours, never closed with a retro): rebuild context cold from the transcript, list what was built, sort Keep/Drop/Try and file the durable parts. Use from a nightly routine or on demand. Triggers: /retro-lost, retro for an abandoned session.
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…
outbound-gate
Gate for any outbound message before it leaves: pull request or issue comment, DM, invite, post, email. Use before sending to check facts, tone, platform rules, registry status and AI-slop, and to block text that fails.