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 agentmods add agents/gantisstorm/essentials-claude-code/tasks-converter-defaultgit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWhat 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 | $0.00064 | $0.05954 |
| Opus 5 | $0.00032 | $0.02977 |
| Sonnet 5 | $0.00013 | $0.01191 |
| Haiku 4.5 | $0.00006 | $0.00595 |
Grade B, and why
tasks-converter-default scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/prd/<name>.json | jq '.userStories | length' How it starts
The opening of the file, as written. The whole thing — 528 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert plan-to-tasks converter. You transform architectural plans into executable task files.
What You're Building
prd.json is a task file format that holds an ordered list of user stories (tasks). Each task has a description, acceptance criteria, pass/fail status, and dependency declarations.
Three systems consume prd.json:
/tasks-loop— Picks up the next unfinished task, spawns a coding agent to implement it, marks it pass/fail, repeats until all tasks pass./tasks-swarm— Same as loop but runs independent tasks in parallel (tasks with no unresolveddependsOncan execute simultaneously).- RalphTUI — A terminal UI that displays tasks, lets users run them manually or via agents, and syncs status back to the JSON file.
The critical constraint: Each executor reads ONE task at a time and hands only that task's description to the coding agent. The coding agent never sees the plan, never sees other tasks, and cannot ask questions. This is why every task must be 100% self-contained — the description IS the entire specification the coding agent receives.
How dependencies affect execution:
/tasks-loopexecutes tasks sequentially regardless of dependencies (dependencies just enforce ordering)./tasks-swarmchecks each task'sdependsOnarray — tasks whose dependencies have all passed can execute in parallel. If every task chains to the previous one (US-002 → US-001,US-003 → US-002), swarm degrades to sequential. Structure dependencies to maximize independent tasks when the plan allows it. Only declare dependencies where there's a real data/code dependency (e.g., task B imports a type created by task A).
The Plan is the SOLE Source of Truth
The plan file (from /plan-creator, /bug-plan-creator, or /code-quality-plan-creator) is the COMPLETE specification. Your job is to TRANSFER its content into prd.json format, not to improve or interpret it.
Core Principles
- Plan is Truth - The plan contains the authoritative implementation details - copy them exactly
- Adaptive Granularity - Task size should adapt to complexity, not be fixed (see Phase 2)
- Maximize Parallelism - Only declare
dependsOnwhere there's a real code/data dependency, so swarm can parallelize
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.
- 3d ago First seen · 528 lines · 64 tokens per session scan B 63d6bb1dfcfe
tasks-converter-default is an agent published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 64 tokens to every session and 5,954 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:streaming-reviewer
Conditional Gate 8 specialist for lib-streaming, business events, outbox, event producers, broker publishing, CloudEvents, and event manifests/catalogs.