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/pueraeternis/agentic-project-template/plan-creationgit clone --depth 1 https://github.com/pueraeternis/agentic-project-templateWrote 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/commands/pueraeternis/agentic-project-template/plan-creation)<a href="https://agentmods.dev/commands/pueraeternis/agentic-project-template/plan-creation"><img src="https://agentmods.dev/badge/commands/pueraeternis/agentic-project-template/plan-creation.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 | $0.00000 | $0.00398 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
plan-creation 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 4d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Creation Prompt
Create the next implementation plan using the Agentic Engineering Methodology.
Objective
Produce one bounded implementation plan that:
- advances the current roadmap phase;
- remains consistent with the documented architecture;
- follows the documented engineering conventions;
- authorizes exactly one implementation increment.
Repository Context
Review the repository in the following order:
AGENTS.mddocs/project/PROJECT.mddocs/project/ROADMAP.mddocs/project/ARCHITECTURE.mddocs/project/ENGINEERING.md- Relevant ADRs
- Completed implementation plans
docs/project/PROGRESS.md
Understand the current repository state before proposing new work.
Planning Rules
Create exactly one implementation plan.
The plan should:
- implement one logical engineering increment;
- have explicit implementation boundaries;
- define measurable acceptance criteria;
- identify implementation risks;
- define validation requirements;
- remain consistent with the engineering decisions documented in
ENGINEERING.md.
Do not:
- redesign the project;
- redesign the architecture;
- combine multiple roadmap phases;
- introduce speculative work;
- silently expand project scope.
Scope
Clearly define:
- included work;
- excluded work;
- dependencies;
- assumptions;
- engineering constraints.
The implementation agent should not need to infer the intended scope.
Acceptance Criteria
Acceptance criteria should be:
- objective;
- measurable;
- testable;
- observable;
- unambiguous.
A reviewer should be able to determine whether the implementation satisfies the plan.
Validation
Define how the implementation will be validated.
Use the validation strategy documented in ENGINEERING.md.
Examples include:
- unit tests;
- integration tests;
- manual verification;
- documentation review;
- project validation commands.
Deliverable
Produce a complete implementation plan using the repository plan template.
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.
- 4d ago First seen · 107 lines · 0 tokens per session scan A 2f046eb7b516
plan-creation is a command published in the GitHub repository pueraeternis/agentic-project-template (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 398 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-31.
Other commands, from other repositories
init-workspace-flow-documentation
Phase 7 Documentation of init-workspace-flow.
trace-commit
Generate a conventional commit message from the most recent trace.
trace-init
Initialize Codetape in the current project.
trace
Record a semantic trace of recent code changes.
trace-map
Generate architecture documentation from component map.
trace-review
Detect documentation drift and report outdated docs.