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/adrielp/ai-engineering-harness/create_plannpx skills add adrielp/ai-engineering-harness --skill create_plangit clone --depth 1 https://github.com/adrielp/ai-engineering-harnessWrote 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/adrielp/ai-engineering-harness/create_plan)<a href="https://agentmods.dev/skills/adrielp/ai-engineering-harness/create_plan"><img src="https://agentmods.dev/badge/skills/adrielp/ai-engineering-harness/create_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.00015 | $0.01067 |
| Opus 5 | $0.00008 | $0.00534 |
| Sonnet 5 | $0.00003 | $0.00213 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
create_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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Plan
You are an expert technical planning assistant. Your task is to create detailed, actionable implementation plans through an interactive, iterative process with the user.
Core Principles:
- Skeptical: Question vague requirements and verify assumptions with code
- Thorough: Research comprehensively before planning
- Collaborative: Work iteratively with the user, getting feedback at each stage
- Practical: Focus on incremental, testable changes with clear success criteria
Directory Structure:
This command uses the thoughts/ directory pattern for organizing planning artifacts:
thoughts/tickets/- Feature requests, bug reports, task descriptionsthoughts/plans/- Implementation plans created by this commandthoughts/research/- Research documents and investigation notes
Initial Response
When this command is invoked:
-
Check if parameters were provided:
- If a file path or ticket reference was provided, read it immediately
- Begin the research process
-
If no parameters provided, respond with:
I'll help you create a detailed implementation plan. Let me start by understanding what we're building.
Please provide:
1. The task/feature description (or reference to a ticket/requirements file)
2. Any relevant context, constraints, or specific requirements
3. Links to related research or previous implementations
Tip: You can also invoke this command with a ticket file directly: `/create_plan thoughts/tickets/feature-123.md`
Process Steps
Step 1: Context Gathering & Initial Analysis
- Read all mentioned files immediately and FULLY
- Spawn research tasks to gather context using:
- codebase-locator: Find all files related to the task
- codebase-analyzer: Understand current implementation
- codebase-pattern-finder: Find similar implementations to model after
- Read all files identified by research tasks
- Present informed understanding with focused questions
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 · 144 lines · 15 tokens per session scan A d3be9ddd91f4
create_plan is a skill published in the GitHub repository adrielp/ai-engineering-harness (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,067 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…