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 skills add didacrios/ai-coding-protocols --skill plan-initiativegit clone --depth 1 https://github.com/didacrios/ai-coding-protocolsWrote 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/didacrios/ai-coding-protocols/plan-initiative)<a href="https://agentmods.dev/skills/didacrios/ai-coding-protocols/plan-initiative"><img src="https://agentmods.dev/badge/skills/didacrios/ai-coding-protocols/plan-initiative/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/didacrios/ai-coding-protocols/plan-initiative"><img src="https://agentmods.dev/badge/skills/didacrios/ai-coding-protocols/plan-initiative.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00076 | $0.01396 |
| Opus 5.5 | $0.00030 | $0.00558 |
| Sonnet 5.5 | $0.00015 | $0.00279 |
| Haiku 4.5 | $0.00008 | $0.00140 |
Grade A, and why
plan-initiative 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 20d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Initiative
A facilitation skill for Engineering Managers to move from a rough idea to a solid initiative brief. This skill prioritizes thinking quality over document speed: clarify the problem first, then define delivery.
When to Activate
- A user asks to plan, frame, or structure an engineering initiative
- Scope is unclear and needs boundaries before execution
- The team is jumping to solutions without a validated problem statement
- Cross-team dependencies, risk, or ownership boundaries are still fuzzy
Core Concepts
- Outcome before output: Define what change should happen before deciding what to build
- Strict clarification gate: Do not draft until mandatory fields are clear enough
- Scope discipline: In-scope and out-of-scope are equally important
- Risk transparency: Make assumptions, unknowns, and dependency criticality explicit
- Single artifact focus: Produce one initiative brief, not multiple parallel documents
Detailed Guidance
Phase 1: Deep discovery (strict-stop mode)
Start with the EM's own description, then ask focused questions in small batches. Keep iterating until uncertainty is low across all mandatory fields.
Ask for:
Problem and motivation (mandatory)
- What exact problem are we solving, for whom?
- What evidence exists (signals, incidents, trends, feedback)?
- Why now? What is the forcing function?
- What happens if we do nothing?
Desired outcome (mandatory)
- What must be different in 3-6 months?
- What decision, behavior, or capability does this unlock?
- How would we recognize progress (metric or proxy if available)?
Scope and boundaries (mandatory)
- What is explicitly in scope?
- What is explicitly out of scope?
- What are the ownership boundaries and decision rights?
Delivery shape
- Is discovery needed before build?
- Can value be delivered incrementally?
- Which parts are sequential vs parallel?
Team, dependencies, and constraints
- Which teams are involved?
- Which dependencies are critical path vs non-critical?
- What constraints exist (timeline, staffing, budget, architecture, compliance)?
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.
- 20d ago Changed · -1 lines · +49 tokens per session 0ea9d76a05e2
- 2mo ago First seen · 194 lines · 27 tokens per session scan A 1d0d53976b89
plan-initiative is a skill published in the GitHub repository didacrios/ai-coding-protocols (2 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 1,396 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…