ariadne: Command for Claude Code

.claude/commands/next-in-epic-11.md

next-in-epic-11 is a command for Claude Code from CRJFisher/ariadne. It costs 0 tokens per session (134 once invoked), scanned A, original, MIT.

A command for continuing with the next task in an Epic 11 development workflow. It directs the agent to follow the task documents and finish the work thoroughly.

In plain words
What is it for?
Use it to read and update task notes, implement the next task, check project structure and skipped work, create follow-up subtasks, and commit the changes.
Why use it?
It keeps implementation aligned with the project's task list, architecture, processing pipeline, tests, follow-up work, and commits.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is CRJFisher/ariadne's own configuration. It tells Claude Code how to work on ariadne itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ariadne configures →

Reuse

Borrowing it

Nothing to install: this file belongs to CRJFisher/ariadne. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/CRJFisher/ariadne/main/.claude/commands/next-in-epic-11.md
Clone the repo
git clone --depth 1 https://github.com/CRJFisher/ariadne

Made for: Claude Code.

Wrote 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.

agentmods badge for next-in-epic-11

README.md
[![agentmods](https://agentmods.dev/badge/commands/crjfisher/ariadne/next-in-epic-11/github.svg)](https://agentmods.dev/commands/crjfisher/ariadne/next-in-epic-11)
Your own site
<a href="https://agentmods.dev/commands/crjfisher/ariadne/next-in-epic-11"><img src="https://agentmods.dev/badge/commands/crjfisher/ariadne/next-in-epic-11/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.

agentmods 80×15 button for next-in-epic-11

Your own site · 80×15
<a href="https://agentmods.dev/commands/crjfisher/ariadne/next-in-epic-11"><img src="https://agentmods.dev/badge/commands/crjfisher/ariadne/next-in-epic-11.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 134 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00134
Opus 5 $0.00000 $0.00067
Sonnet 5 $0.00000 $0.00027
Haiku 4.5 $0.00000 $0.00013

Measured 11d ago against content hash 969c1bab8fca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

next-in-epic-11 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 11d 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.

.claude/commands/next-in-epic-11.md · 10 lines

What it actually says

Continue with the next task

  • read the task's to-do items and complete them fully, thoroughly, without cutting any corners
  • update the task doc as you go including any insights or key decisions
  • double check that the files follow the @docs/Architecture.md structure e.g. tests are colocated with the code, not in the /tests folder
  • double check the @docs/PROCESSING_PIPELINE.md doc to see how the next task fits into the overall processing
  • commit changes
  • check if any work was skipped during the task implementation. If there were any follow-up tasks, create them as sub-tasks

ultrathink

Changes

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.

  1. 11d ago First seen · 10 lines · 0 tokens per session scan A 969c1bab8fca

Subscribe to this mod's changes

next-in-epic-11 is a command published in the GitHub repository CRJFisher/ariadne (22 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 134 tokens. 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.