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 commands/wildchildforlife/lantern/plangit clone --depth 1 https://github.com/WildChildForLife/lanternWhat 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.00009 | $0.00349 |
| Opus 5 | $0.00005 | $0.00175 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
plan 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 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.
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.
This is a copy
100% identical to plan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Create a comprehensive task plan for the given development work. Break down complex tasks into manageable, actionable steps.
Planning Process
-
Analysis Phase
- Use Read, Grep, and Glob tools to understand the current codebase
- Identify existing patterns, conventions, and dependencies
- Check git status to understand current state
-
Task Breakdown
- Decompose the main objective into specific, actionable tasks
- Each task should be completable within a reasonable timeframe
- Include both implementation and verification steps
-
Create Todo List
- Use TodoWrite tool to create a structured task list
- Set all tasks to "pending" status initially
- Include both content (imperative form) and activeForm (present continuous)
- Order tasks by logical dependency and priority
-
Task Categorization
- Implementation tasks (new features, bug fixes)
- Testing and verification tasks
- Documentation updates (if required)
- Build and deployment tasks
Task Planning Guidelines
- Make tasks specific and measurable
- Include prerequisite checks where needed
- Add validation steps after implementation
- Consider potential blockers and alternatives
- Ensure each task has clear completion criteria
Example Task Structure
For each task in the todo list:
- content: "Implement user authentication middleware"
- activeForm: "Implementing user authentication middleware"
- status: "pending"
Always start with research and analysis tasks before moving to implementation.
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 · 49 lines · 9 tokens per session scan A 3bc93c4b5053
plan is a command published in the GitHub repository WildChildForLife/lantern (22 stars, last pushed 8d ago), licensed MIT. It adds 9 tokens to every session and 349 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to plan, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
release
Bump version, tag, push, and create a GitHub release with auto-generated notes.
reviewzy
File user-facing copy for human approval, then apply it in a later session.
autobot-stop
Stop an autobot session (kill tmux and dev environment, but keep the worktree).
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
build
Run full verification pipeline.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).