copilot-setting: Skill for Claude Code

.github/skills/plan/SKILL.md

plan is a skill for Claude Code, Codex from zexion7873/copilot-setting. It costs 88 tokens per session (1,408 once invoked), scanned A, original, MIT.

A workflow for creating a phased implementation plan before writing code. It first clarifies unclear requirements, then records affected files, risks, alternatives, and the agreed scope.

In plain words
What is it for?
Planning new features or other coding tasks, especially when the goal, affected parts, or acceptance criteria are unclear.
Why use it?
It helps expose missing decisions early, so implementation does not depend on guesses about requirements or project boundaries.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is zexion7873/copilot-setting's own configuration. It tells Claude Code and Codex how to work on copilot-setting itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything copilot-setting configures →

Reuse

Borrowing it

Nothing to install: this file belongs to zexion7873/copilot-setting. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zexion7873/copilot-setting/main/.github/skills/plan/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/zexion7873/copilot-setting

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/zexion7873/copilot-setting/plan/github.svg)](https://agentmods.dev/skills/zexion7873/copilot-setting/plan)
Your own site
<a href="https://agentmods.dev/skills/zexion7873/copilot-setting/plan"><img src="https://agentmods.dev/badge/skills/zexion7873/copilot-setting/plan/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.

agentmods 80×15 button for plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/zexion7873/copilot-setting/plan"><img src="https://agentmods.dev/badge/skills/zexion7873/copilot-setting/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,408 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00088 $0.01408
Opus 5.5 $0.00035 $0.00563
Sonnet 5.5 $0.00018 $0.00282
Haiku 4.5 $0.00009 $0.00141

Measured 2mo ago against content hash 009224c7a5d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.github/skills/plan/SKILL.md · 135 lines

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:

  1. Parse the request — extract goal (may be implicit), scope (modules/files/features involved), constraints (deadlines, tech limitations, backward compatibility)
  2. Identify gaps — flag anything that would force guessing during implementation: missing acceptance criteria, ambiguous scope boundaries, unstated assumptions about existing behavior, conflicting requirements
  3. 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.
  4. 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

  1. Scan codebase for existing patterns relevant to the goal
  2. Identify affected files and modules
  3. 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-NNN identifiers
  • Approach: phased, each phase has a measurable goal
  • Files: real paths from the codebase scan
  • Risks: with specific mitigation, not generic "might be hard"

Read the full file on GitHub · 135 lines

Changes

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.

  1. 2mo ago First seen · 135 lines · 88 tokens per session scan A 009224c7a5d1

Subscribe to this mod's changes

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.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.

Related

plan compared with skills from other repositories

plan next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
planzexion7873/copilot-settingSkill11mo agoMITA88Claude Code, Codex
jira-cliCode-and-Sorts/awesome-copilot-agentsSkill5936mo agoCC0-1.0A60Claude Code, Codex
azure-pricesCode-and-Sorts/awesome-copilot-agentsSkill5936mo agoCC0-1.0A90Claude Code, Codex
calculatorCode-and-Sorts/awesome-copilot-agentsSkill5936mo agoCC0-1.0A50Claude Code, Codex
az-cliCode-and-Sorts/awesome-copilot-agentsSkill5936mo agoCC0-1.0A79Claude Code, Codex
plan-tasksavedpixel/ai-agent-rules-generatorSkill86mo agoMITA45Claude Code, Codex
commitsavedpixel/ai-agent-rules-generatorSkill86mo agoMITA40Claude Code, Codex