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/snyk/snyk-ls/create-implementation-plannpx skills add snyk/snyk-ls --skill create-implementation-plangit clone --depth 1 https://github.com/snyk/snyk-lsWrote 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/snyk/snyk-ls/create-implementation-plan)<a href="https://agentmods.dev/skills/snyk/snyk-ls/create-implementation-plan"><img src="https://agentmods.dev/badge/skills/snyk/snyk-ls/create-implementation-plan.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.00045 | $0.00906 |
| Opus 5 | $0.00023 | $0.00453 |
| Sonnet 5 | $0.00009 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
create-implementation-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 5d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Implementation Plan
Creates implementation plans using the official project template with session hand-off support, TDD workflow, and progress tracking.
Quick Start
- Extract issue ID from branch:
git branch --show-current(format:XXX-XXXX) - Read Jira issue for context and acceptance criteria
- Create plan file:
${issueID}_implementation_plan.md(root directory) - Create
tests.jsonfor test scenario tracking - Create mermaid diagrams in
docs/diagrams/ - STOP and wait for user confirmation
Template Location
Use template from: docs/templates/IMPLEMENTATION_PLAN_TEMPLATE.md
Replace all {{TICKET_ID}} and {{TICKET_TITLE}} placeholders with actual values.
Files to Create
| File | Location | Purpose |
|---|---|---|
| Implementation plan | ${issueID}_implementation_plan.md |
Main plan document |
| Test tracking | tests.json |
Track test scenarios across sessions |
| Flow diagrams | docs/diagrams/${issueID}_*.mmd |
Mermaid source files |
All these files are gitignored - NEVER commit them.
Key Sections to Complete
1. SESSION RESUME (Critical for hand-off)
- Update Quick Context with ticket info and branch
- Fill Current State table
- List Next Actions
- Update Current Working Files table
2. Phase 1: Planning
- 1.1 Requirements Analysis: List changes, error handling, files to modify/create
- 1.2 Schema/Architecture Design: Add schemas, data structures
- 1.3 Flow Diagrams: Create mermaid files, generate PNGs
3. Phase 2: Implementation (Outside-in TDD)
- Use testing skill
- CRITICAL: use outside-in TDD
- Enforce strict test order:
- Smoke tests (E2E behavior)
- Integration tests (cross operating system behaviour, integrative behaviour)
- Unit tests
- Break into checkpoint steps (completable in one session)
- Each step: tasks, tests to write FIRST, commit message
- Reference test IDs from
tests.json - Add a plan self-check: integration tests must appear before unit tests
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.
- 5d ago First seen · 117 lines · 45 tokens per session scan A 4e63b62930a3
create-implementation-plan is a skill published in the GitHub repository snyk/snyk-ls (83 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 906 once invoked, about $0.0002 per session on Opus 5. 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.
Other skills, from other repositories
tasks
Use when asked to work on or track a task in the Tasks plugin, when the prompt mentions a task key such as ABC-12, or when work needs task comments, attachments, delegation tracking, or status updates.
planning
Create structured plan documents and track work items using YAML frontmatter. Use when the user wants to plan a feature, track progress, log bugs/tasks/ideas, or organize project work.
feedback-intake
Help the user file a bug report or feature request for Nimbalyst. Activates when the user opens the in-app feedback flow or runs /feedback:bug-report or /feedback:feature-request. Coordinates evidence gathering, anonymization, and posting to GitHub Issues.
github
Complete guide for the GitHub plugin — REST API access for repositories, issues, pull requests, actions, releases, and search using a GitHub Personal Access Token.
report
Report the current repository and task state, evidence, developer action, and next step when work is long-running, blocked, needs review, or ready for handoff.
openspec-implementation
按顺序推进已批准的规格提案，结合测试与校验完成实现。当实现变更、应用提案、执行规格任务或基于已批准计划构建时使用。触发词包括 "openspec implement"、"implement"、"apply change"、"execute spec"、"work through tasks"、"build feature"、"start implementation"。.