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 skills/pueraeternis/agentic-project-template/plan-implementationnpx skills add pueraeternis/agentic-project-template --skill plan-implementationgit 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/skills/pueraeternis/agentic-project-template/plan-implementation)<a href="https://agentmods.dev/skills/pueraeternis/agentic-project-template/plan-implementation"><img src="https://agentmods.dev/badge/skills/pueraeternis/agentic-project-template/plan-implementation.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.00814 |
| Opus 5 | $0.00000 | $0.00407 |
| Sonnet 5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
plan-implementation 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.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Implementation
Purpose
This skill implements one approved implementation plan.
Implementation is the execution of an approved engineering contract.
The objective is to translate documented project intent into production-ready implementation while preserving architecture, engineering conventions, and repository consistency.
Implementation should satisfy the approved plan without introducing unrelated work.
Lifecycle Stage
Plan Review
↓
Plan Implementation
↓
Code Review
Plan Implementation realizes the approved implementation increment.
It does not redesign the project.
Role
Primary role:
Implementation Agent
When to Use
Use this skill when:
- an implementation plan has been approved;
- implementation has been authorized;
- required project documentation exists.
Do not begin implementation before Plan Review has approved the plan.
Inputs
Required:
- approved implementation plan;
PROJECT.md;ROADMAP.md;ARCHITECTURE.md;ENGINEERING.md.
Additional references:
- ADRs;
- completed plans;
- current repository state.
The approved implementation plan is the authoritative engineering contract.
Outputs
Produce:
- production-ready implementation;
- tests where appropriate;
- updated documentation when required;
- completed implementation checklist;
- implementation ready for Code Review.
Procedure
Step 1 — Understand the Engineering Contract
Review the implementation plan.
Verify:
- objective;
- scope;
- out-of-scope items;
- acceptance criteria;
- validation requirements;
- implementation constraints.
Implementation must not begin until the contract is fully understood.
Step 2 — Build Project Context
Review:
- project definition;
- roadmap;
- architecture;
- engineering design;
- ADRs;
- current implementation.
Understand:
- why the implementation exists;
- architectural boundaries;
- engineering conventions;
- existing repository structure.
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 · 246 lines · 0 tokens per session scan A cbdb2eda78fd
plan-implementation is a skill 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 814 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 skills, from other repositories
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
gsap-scrolltrigger
Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…
gsap-core
Official GSAP skill for the core API — gsap.to(), from(), fromTo(), easing, duration, stagger, defaults, gsap.matchMedia() (responsive, prefers-reduced-motion). Use when the user asks for a JavaScript animation library, animation in React/Vue/vanilla, GSAP tweens, easing, basic animation, responsive or reduced-motion…
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.
lyria
Generate and validate music with Google Lyria 3 through the Gemini Interactions API. Use before calling OpenMontage googlemusic, designing Lyria 3 Clip or Pro prompts, using image-to-music or custom lyrics, choosing between Lyria 3 and Lyria RealTime, diagnosing Google music-generation failures, or preparing…
comfyui
Use when working with ComfyUI workflows in OpenMontage, including comfyuiimage/comfyuivideo/comfyuimusic, custom workflowjson/workflowpath inputs, outputnode selection, missing model setup, LoRAs, low-VRAM workflow choices, and community workflow imports.