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/matrixfounder/agentic-development/skill-planning-formatnpx skills add MatrixFounder/Agentic-development --skill skill-planning-formatgit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWhat 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.00023 | $0.00450 |
| Opus 5 | $0.00012 | $0.00225 |
| Sonnet 5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
skill-planning-format 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 2d 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.
What it actually says
Planning Output Format
Purpose: Defines the rigid structure for planning documents effectively.
1. Red Flags (Anti-Rationalization)
STOP if you are thinking:
- "I'll plan the details later" -> WRONG. "Later" means "Never". Breakdown must happen NOW.
- "This task is too simple for a file" -> WRONG. Every unit of work needs a
task-*.mdfile for tracking. - "I'll use my own format" -> WRONG. The Orchestrator relies on this specific structure.
2. Development Plan Structure (docs/PLAN.md)
The Main Plan acts as the "Table of Contents" for the feature.
[!TIP] Use the template at
assets/templates/plan_md_template.md.
3. Detailed Task Description Structure
For each task in the plan, you must create a separate file: docs/tasks/task-{ID}-{SubID}-{slug}.md.
[!TIP] Use the template at
assets/templates/task_md_template.md.
Rationalization Table
| Agent Excuse | Reality / Counter-Argument |
|---|---|
| "I don't know the implementation details yet" | That is why you are in PLANNING mode. Research until you know. |
| "Writing 5 files takes too long" | Fixing a disorganized codebase takes 10x longer. |
4. Result Structure Rules
docs/PLAN.mdfile — general development plan with task sequence.docs/tasks/task-{ID}-{SubID}-{Slug}.mdfiles — detailed descriptions of each task.- CRITICAL: Use only RELATIVE paths for file links (e.g.,
[Link](docs/tasks/file.md)), never absolute.
5. Resources
assets/templates/: Standard markdown templates.examples/: Real-world planning examples.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 44 lines · 23 tokens per session scan A 195eb245c271
skill-planning-format is a skill published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 23 tokens to every session and 450 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-31.
Other skills, from other repositories
add-tests
Generates tests for existing code. Analyzes the target function, method, or class to identify the happy path, error cases, and edge cases, then writes test cases following the project's testing framework and naming conventions. Invoked when the user asks to add tests, write tests, cover code, or increase coverage.
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
nunit-api-design
Use when adding or modifying public API surface in NUnit — new or changed constraints, attributes, assertions, helpers, or any type/member visibility change. Covers the conventions NUnit maintainers enforce for types that ship to consumers of the framework.
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
company-hiring-intelligence
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents. Use whenever a user wants to understand a company's strategic direction from hiring signals, do competitive intelligence, figure out a tech stack from job…
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…