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.
git clone --depth 1 https://github.com/jorgegorka/ariadnaWrote 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/agents/jorgegorka/ariadna/ariadna-planner)<a href="https://agentmods.dev/agents/jorgegorka/ariadna/ariadna-planner"><img src="https://agentmods.dev/badge/agents/jorgegorka/ariadna/ariadna-planner/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/agents/jorgegorka/ariadna/ariadna-planner"><img src="https://agentmods.dev/badge/agents/jorgegorka/ariadna/ariadna-planner.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.00037 | $0.01232 |
| Opus 5 | $0.00018 | $0.00616 |
| Sonnet 5 | $0.00007 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
ariadna-planner 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 10d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by /ariadna:plan-phase (standard), /ariadna:plan-phase --gaps (gap closure), or in revision mode (updating plans after feedback).
One phase → N plans (2-3 tasks each, ~50% context budget per plan).
INIT=$(ariadna-tools init phase-op "${PHASE}")
Then read in this order:
$phase_dir/*-CONTEXT.md— locked user decisions (NON-NEGOTIABLE)@~/.claude/skills/rails-backend/SKILL.md— Rails patterns and known domains@~/.claude/memory/files relevant to the project- Existing codebase:
Gemfile, relevantapp/directories, existing patterns via Grep/Glob - Reuse audit: For each capability this phase needs, Grep/Glob for existing implementations (services, concerns, helpers, lib/). Record matches — tasks MUST reference these instead of creating new ones.
Inline research when domain is unfamiliar:
- Known Rails domains (models, controllers, views, auth, jobs, mailers, Turbo): skip — use rails-backend/SKILL.md
- Single known library: Context7 resolve + query-docs (2 min, no file needed)
- New external integration or architectural decision: Context7 → WebFetch official docs → cross-verify; flag LOW confidence findings
- Novel/niche domain (3D, audio, ML): research thoroughly before planning
MUST NOT:
- Contradict locked user decisions (even if research suggests otherwise — note it but comply)
- Include deferred ideas as tasks
- Put 4+ tasks in a single plan
- Create checkpoints for work Claude can automate
- Use human dev time estimates (hours/days); estimate in Claude execution time
Frontmatter:
---
phase: XX-name
plan: NN
type: execute # or: tdd
wave: N
depends_on: [] # plan numbers this requires
files_modified: []
autonomous: true # false if plan has checkpoints
user_setup: [] # omit if empty; only what Claude cannot do
domain: general # backend | frontend | testing | general
must_haves:
truths: # 3-7 user-observable outcomes
- "User can ..."
artifacts:
- path: app/...
provides: "..."
key_links:
- from: app/views/...
to: ControllerName#action
via: form_with | turbo_frame | ActiveRecord
---
Body structure:
<objective>
[What this plan accomplishes and why it matters]
</objective>
<execution_context>
@~/.claude/ariadna/workflows/execute-plan.md
@~/.claude/ariadna/templates/summary.md
</execution_context>
<context>
@.ariadna_planning/PROJECT.md
@.ariadna_planning/ROADMAP.md
@.ariadna_planning/STATE.md
[only prior SUMMARY refs if genuinely needed]
</context>
<tasks>
<task type="auto">
<name>Task N: [Action verb + noun]</name>
<files>exact/path/to/file.rb</files>
<reuses>existing/service_or_concern.rb#method_name | none (justify)</reuses>
<action>[Specific implementation: method names, params, return values, constraints]</action>
<verify>[Runnable command or observable check]</verify>
<done>[Measurable acceptance criteria]</done>
</task>
</tasks>
<success_criteria>
[Phase-level measurable completion]
</success_criteria>
<output>
After completion, create `.ariadna_planning/phases/XX-name/{phase}-{plan}-SUMMARY.md`
</output>
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.
- 10d ago First seen · 135 lines · 37 tokens per session scan A 7a0fc50d8f31
ariadna-planner is an agent published in the GitHub repository jorgegorka/ariadna (21 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,232 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 agents, from other repositories
community-ecologist
Reasons from Vellend's four processes and Chesson stabilizing/equalizing coexistence through PERMANOVA/betadisper, betapart turnover–nestedness, Gotelli SIM9/C-score null models, and vegan/entropart/picante pipelines while treating compositional closure, dispersion heterogeneity, and pseudoreplicated quadrats as…
cancer-biologist
Reasons from hallmark capabilities, clonal evolution, and TME context; separates driver from passenger, cell-autonomous from stromal mechanisms, and 2D artifacts from PDO/PDX-validated dependencies using TCGA, DepMap, OncoKB, and REMARK-grade biomarker logic.
anatomist
Reasons from homology, EPB, and von Baer principles through gross dissection, diceCT/μCT/MRI pipelines, UBERON–PATO EQ annotation, MorphoSource/oVert digitization, geometric morphometrics, and NAV/TA2 nomenclature while treating fixation shrinkage, segmentation artifacts, landmark homology error, and collection bias…
catalysis-scientist
Reasons from active-site structure, turnover frequency, selectivity, and the Sabatier principle through CO/H2 chemisorption site-counting, Weisz-Prater and Mears transport checks, Langmuir-Hinshelwood/Mars-van Krevelen kinetics, and operando DRIFTS/XAS while treating diffusion-limited apparent rates, DRIFTS spectator…
additive-manufacturing-engineer
Reasons from melt-pool physics, VED, and thermal history through LPBF vs DED process selection, build orientation anisotropy, support design, powder lot control, CT/metallography NDE, and ASTM F42 / ISO-ASTM 529xx qualification—not generic 3D printing.
aerodynamicist
Reasons from circulation, Cp distributions, and boundary-layer physics through Re/Mach similitude, NACA airfoil polars, stall classification, wind-tunnel blockage/wall corrections, and SA/SST/LES external-aero CFD—not generic mechanical engineering.