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/zexion7873/copilot-setting/plannpx skills add zexion7873/copilot-setting --skill plangit clone --depth 1 https://github.com/zexion7873/copilot-settingWrote 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/zexion7873/copilot-setting/plan)<a href="https://agentmods.dev/skills/zexion7873/copilot-setting/plan"><img src="https://agentmods.dev/badge/skills/zexion7873/copilot-setting/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.00088 | $0.01408 |
| Opus 5 | $0.00044 | $0.00704 |
| Sonnet 5 | $0.00018 | $0.00282 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade A, and why
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 3d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan — Workflow
Structured implementation plan. Clarify vague requirements first (Phase 1), then plan.
Phase 1 — Clarify Requirements
Skip this phase when the request is already well-defined. When it is vague, ambiguous, or missing critical information:
- Parse the request — extract goal (may be implicit), scope (modules/files/features involved), constraints (deadlines, tech limitations, backward compatibility)
- Identify gaps — flag anything that would force guessing during implementation: missing acceptance criteria, ambiguous scope boundaries, unstated assumptions about existing behavior, conflicting requirements
- Ask numbered questions — 3–7 questions; each states what is unclear, offers 2–3 concrete options when possible, and marks a recommended default if one exists. Do NOT ask questions the codebase can answer — scan first, ask only what code cannot tell you.
- Confirm understanding — after answers, record the confirmed scope before planning:
## Confirmed Understanding
- Goal: ...
- Scope: ...
- Constraints: ...
- Out of scope: ...
- Open items: ... (if any remain)
Phase 2 — Gather Context
- Scan codebase for existing patterns relevant to the goal
- Identify affected files and modules
- Note constraints: tech stack (Java 8 / Maven / Spring 3.2 / Hibernate 4.2), backward compatibility, data migration needs
Phase 3 — Classify Scope
| Scope | Definition | Plan depth |
|---|---|---|
| Small | 1–3 files, single module | Lightweight: goal + approach + files (template sections 1–3) |
| Medium | 4–10 files, cross-module | Standard: full template |
| Large | 10+ files, schema change, or API change | Full template + mandatory red-team depth (≥2 ASM/GAP entries) + migration/rollback plan (dedicated phases in section 2, RISK entries in section 5) |
Phase 4 — Draft Plan
Fill the template below (Small scope: sections 1–3 only; Medium+: full template). Every section must be concrete:
- Requirements: traceable
REQ-NNN/CON-NNNidentifiers - Approach: phased, each phase has a measurable goal
- Files: real paths from the codebase scan
- Risks: with specific mitigation, not generic "might be hard"
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.
- 3d ago First seen · 135 lines · 88 tokens per session scan A 009224c7a5d1
plan is a skill published in the GitHub repository zexion7873/copilot-setting (1 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,408 once invoked, about $0.0004 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
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
azure-prices
Look up and compare Azure service pricing using the Azure Retail Prices API. Use this skill whenever the user asks about Azure costs, pricing, rates, or wants to compare prices across regions or services — even if they don't say "pricing" explicitly. Trigger for questions like "how much does a D2 v2 VM cost?"…
calculator
Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.
az-cli
Use the Azure CLI (az) to manage Azure resources from the command line. Trigger this skill whenever the user asks to create, configure, manage, deploy, or interact with any Azure resource — even if they don't explicitly mention "az cli". Also trigger when the user asks about Azure CLI commands, syntax, or wants to…
plan-task
Create a detailed implementation plan before coding. Use when starting a new feature, multi-step refactor, or complex task. Invoked by saying "plan", "create a plan", or "plan this task".
commit
Stage, commit, and push code changes with branch safety and explicit staging. Use when ready to commit work. Invoked by saying "commit", "push", or "commit and push".