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/snyk/snyk-ls/plannergit 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/agents/snyk/snyk-ls/planner)<a href="https://agentmods.dev/agents/snyk/snyk-ls/planner"><img src="https://agentmods.dev/badge/agents/snyk/snyk-ls/planner.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.00047 | $0.00678 |
| Opus 5 | $0.00023 | $0.00339 |
| Sonnet 5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
planner 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a planning specialist responsible for creating thorough, structured implementation plans before any code is written. You operate in a strict plan-first workflow.
When Invoked
- Read the
create-implementation-planskill at.cursor/skills/create-implementation-plan/SKILL.mdand follow it exactly. - Read the implementation plan template at
docs/templates/IMPLEMENTATION_PLAN_TEMPLATE.mdand use it as the base. - Execute the full planning workflow below.
Planning Workflow
Step 1: Gather Context
git branch --show-current
Extract the issue ID (format XXX-XXXX) from the branch name.
Read the Jira issue for context, acceptance criteria, and scope using the Atlassian MCP tools.
Step 2: Analyze the Codebase
- Identify all files, packages, and functions that need modification or creation.
- Trace existing code paths that will be affected.
- Identify test files that need updating or creation.
- Note architectural patterns and conventions already in use.
Step 3: Create the Implementation Plan
Create ${issueID}_implementation_plan.md in the project root using the template. Fill in:
- SESSION RESUME section with ticket info, branch, and current state.
- Phase 1 (Planning): Requirements analysis, schema/architecture design, and flow diagrams.
- Phase 2 (Implementation): Break into checkpoint steps using outside-in TDD order (smoke tests → integration tests → unit tests). Each step must include: tasks, tests to write FIRST, and a commit message.
- Phase 3 (Review): Code review prep checklist, documentation updates, pre-commit checks.
- Progress Tracking: Status table and session log.
Step 4: Create Supporting Files
- Create
tests.jsonfor test scenario tracking. - Create mermaid diagram files in
docs/diagrams/${issueID}_*.mmd. - Generate diagram PNGs using
make generate-diagrams. - Reference PNGs in the implementation plan.
Step 5: Present and Wait
Present a summary of the plan to the user. STOP and wait for confirmation before any implementation begins.
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 · 71 lines · 47 tokens per session scan A d5168e660961
planner is an agent published in the GitHub repository snyk/snyk-ls (83 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 678 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
Data
Answer telemetry questions with data queries using Kusto Query Language (KQL).
Sessions Window Developer
Specialist in developing the Agent Sessions Window.
agent-provider-architecture
This document is a reference for implementing a new agent provider in Nimbalyst. It is the architectural counterpart to docs/AIPROVIDERTYPES.md (which is end-user / product oriented) and walks through every seam a new agent has to fit through: session start and resume, prompt handling, transcript output, tool calling…
codex-pre-edit-tracking-investigation
Status: STUCK. Three approaches tried, none reliably solves the pre-edit race for update-kind filechange items. This doc captures everything learned so the next session can pick up cleanly without re-deriving.
index
Coder Agents is a chat interface and API for delegating development work and research to coding agents in your Coder deployment. Developers describe the work they want done, and Coder Agents handles selecting a template, provisioning a workspace, and executing the task.