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/nikiforovall/github-copilot-rules/planning-with-filesnpx skills add NikiforovAll/github-copilot-rules --skill planning-with-filesgit clone --depth 1 https://github.com/NikiforovAll/github-copilot-rulesWrote 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/nikiforovall/github-copilot-rules/planning-with-files)<a href="https://agentmods.dev/skills/nikiforovall/github-copilot-rules/planning-with-files"><img src="https://agentmods.dev/badge/skills/nikiforovall/github-copilot-rules/planning-with-files.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.00023 | $0.01029 |
| Opus 5 | $0.00012 | $0.00515 |
| Sonnet 5 | $0.00005 | $0.00206 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
planning-with-files 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning with Files
Use persistent markdown files as external memory for complex tasks. Files survive context limits and session boundaries.
Use TodoWrite to decompose phases into executable tasks. Before closing session, use Question to confirm findings, decisions, and deliverables are satisfactory.
When to Use
- User explicitly requests planning/tracking with files
- Complex multi-session tasks
- Research-heavy work requiring persistent notes
- Tasks where decisions and rationale need to be preserved
When NOT to Use
- Simple single-session tasks (use Plan agent instead)
- Quick fixes or small changes
- Tasks with clear requirements needing no research
Directory Convention
All planning files go in _plans/ with date-prefixed task folders:
_plans/
2026-01-08-dark-mode-toggle/
plan.md
research.md
decisions.md
2026-01-09-api-auth-refactor/
plan.md
scratch.md
Naming: YYYY-MM-DD-task-name (kebab-case, concise description)
File Types
Create files based on what the task needs, not a fixed pattern:
| Type | When to Create | Content |
|---|---|---|
plan.md |
Always | Goal, phases, status, errors encountered |
research.md |
Research-heavy tasks | Sources, findings, synthesized data |
decisions.md |
Tradeoff decisions | ADRs, options considered, rationale |
scratch.md |
Complex reasoning | Drafts, working notes, exploratory code |
[deliverable].md |
Final outputs | Reports, summaries, documentation |
plan.md Template
# Plan: [Brief Description]
## Goal
[One sentence describing the end state]
## Phases
- [ ] Phase 1: [Description]
- [ ] Phase 2: [Description]
- [ ] Phase 3: [Description]
## Status
**Current:** [What's happening now]
## Decisions
- [Decision]: [Rationale]
## Errors Encountered
- [Error]: [Resolution]
research.md Template
# Research: [Topic]
## Sources
- [Source]: [Key findings]
## Findings
### [Category]
- [Finding]
What ships with it
2 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.
- 5d ago First seen · 165 lines · 23 tokens per session scan A b0fa571fd361
planning-with-files is a skill published in the GitHub repository NikiforovAll/github-copilot-rules (131 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,029 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
fuzzy-selecting
Use when choosing interactively from search results, files, processes, or any command output with preview capabilities.
replacing-text
Use when performing text find & replace, batch transformations across files, or when JavaScript-style regex syntax is preferred over sed.
searching-text
Use when searching for text patterns across files, finding specific code locations, or getting lines with surrounding context in a single call.
context-management
UTILITY SKILL — Two-mode context-window management. RUNTIME: artifact compression (full/summarized/minimal) used by orchestrator and codegen agents. AUDIT: post-mortem analysis of Copilot debug logs (token profiling, redundancy + hand-off gap detection) used by 11-Context Optimizer. WHEN: "context optimization"…
session-recovery
Find and resume interrupted Copilot CLI sessions using sessionstore queries.
notification-routing
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding.