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 maintenancegit 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/maintenance)<a href="https://agentmods.dev/skills/pariyar07/ariadne/maintenance"><img src="https://agentmods.dev/badge/skills/pariyar07/ariadne/maintenance.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.00051 | $0.01351 |
| Opus 5 | $0.00026 | $0.00675 |
| Sonnet 5 | $0.00010 | $0.00270 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
ariadne:maintenance 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ariadne Maintenance
Use this skill when auditing, repairing, or maintaining a Markdown knowledge vault over time.
Start
- Read root instructions and every applicable ancestor scope instruction through the target.
- Read relevant indexes, agent navigation, health-check procedure, and navigation standard.
- Discover findings read-only. In a multi-scope vault, require a current-turn named or confirmed target before scoped repairs.
- Run
sync_scope_topology.js --checkfor topology findings. Audit/check behavior is always zero-write.
Health Checks
Check for:
- invalid Markdown frontmatter
- invalid
.baseYAML - broken wikilinks, resolving both
.mdand.basefiles - Markdown notes with no incoming or outgoing wikilinks
.basefiles missing fromBases/00 Bases Index.md- important notes missing from folder hubs
- folder hubs missing from agent navigation
- stale inbox items
- stale processing queue items
- decisions without rationale
- generated outputs that should be filed back into the wiki
- entry files or folder hubs becoming too large to scan
- durable folders without
00 ... Index.mdhubs - recurring workstreams missing from task routing
- stale or missing local
AGENTS.mdfiles for specialized folders - promoted scopes missing hubs
- child hubs missing parent links
- parent hubs missing child links
- local Bases missing folder scope filters
- local
AGENTS.mdfiles repeating parent policy instead of local deltas - local queues piling up inside child scopes
- scope indexes becoming full tables of contents instead of navigable maps
Proactive Repair Routing
When you discover a problem during unrelated vault work, surface it instead of letting it become hidden drift:
- State what appears broken.
- Explain why it matters for future agents or human navigation.
- Recommend the smallest next check or skill.
- Say whether you can safely fix it now or need approval.
Use this routing:
- Global discovery, stale registry entrypoints, or missing adapter marker blocks: use
ariadne:global-discoveryand run the Ariadne discovery doctor. - Broken wikilinks, orphan notes, invalid frontmatter, invalid
.baseYAML, unlinked Bases, or validator warnings: useariadne:validatorfirst, then repair with this skill. - Navigation bloat, missing hubs, missing parent-child hub links, task routing drift, or unclear scope boundaries: use
ariadne:navigation. - General inbox, processing, or output buildup: use
ariadne:knowledge-capture. - Research provenance, compilation coverage, stale synthesis, unresolved research questions, evidence roles, circular corroboration, or older pipeline drift: use
ariadne:research-stewardship. - Missing repeatable research infrastructure inside a scope: use
ariadne:research-pipeline.
What ships with it
1 file 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.
- 7d ago First seen · 120 lines · 51 tokens per session scan A 4daa47786fa3
ariadne:maintenance is a skill published in the GitHub repository pariyar07/ariadne (20 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,351 once invoked, about $0.0003 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
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…
wiki-cli
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.