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 skills add Poorgramer-Zack/copilot-cli-things --skill copilot-cli-configuratorgit clone --depth 1 https://github.com/Poorgramer-Zack/copilot-cli-thingsWrote 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/poorgramer-zack/copilot-cli-things/copilot-cli-configurator)<a href="https://agentmods.dev/skills/poorgramer-zack/copilot-cli-things/copilot-cli-configurator"><img src="https://agentmods.dev/badge/skills/poorgramer-zack/copilot-cli-things/copilot-cli-configurator/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.
<a href="https://agentmods.dev/skills/poorgramer-zack/copilot-cli-things/copilot-cli-configurator"><img src="https://agentmods.dev/badge/skills/poorgramer-zack/copilot-cli-things/copilot-cli-configurator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00079 | $0.03183 |
| Opus 5.5 | $0.00032 | $0.01273 |
| Sonnet 5.5 | $0.00016 | $0.00637 |
| Haiku 4.5 | $0.00008 | $0.00318 |
Grade B, and why
copilot-cli-configurator scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Omit `tools` or use `tools: ["*"]` → all tools enabled How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot CLI Configurator
Set up and configure GitHub Copilot CLI customization surfaces. For creating skills, extensions, or MCP servers from scratch, use the dedicated skill-creator, create-extension, or mcp-builder skills instead.
Choosing the Right Customization
| Goal | Use |
|---|---|
| Copilot should always follow repo conventions | Custom instructions |
| Repeatable workflow invoked on demand | Skills |
| Guardrails, policy, or automation around tool use | Hooks |
| External tools and data sources | MCP servers |
| Specialist persona with constrained toolset | Custom agents |
| Custom tools, programmatic hooks, model switching | Extensions |
| Bundle of functionality to distribute | Plugins |
Read references/feature-comparison.md for detailed trade-offs between each surface.
1. Custom Instructions
Persistent guidance loaded at session start — tells Copilot how to behave across all tasks.
File Locations
| Type | File | Location |
|---|---|---|
| Repository-wide | copilot-instructions.md |
.github/ |
| Path-specific | *.instructions.md |
.github/instructions/ (supports subdirs) |
| Agent instructions | AGENTS.md |
Repo root, cwd, or COPILOT_CUSTOM_INSTRUCTIONS_DIRS paths |
| Local/personal | copilot-instructions.md |
~/.copilot/ |
Also supports CLAUDE.md and GEMINI.md at repo root.
Path-Specific Instructions
Require YAML frontmatter with applyTo glob:
---
applyTo: "**/*.ts,**/*.tsx"
---
Use strict TypeScript with no `any` types. Prefer interfaces over type aliases.
Optional excludeAgent field to exclude "code-review" or "coding-agent".
When to Use
- Style and quality rules (e.g., "prefer small PRs, write tests")
- Repository conventions (e.g., "use pnpm, keep CHANGELOG.md updated")
- Communication preferences (e.g., "explain tradeoffs briefly")
When NOT to Use
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.
- 2mo ago First seen · 400 lines · 79 tokens per session scan B 73b7ee389930
copilot-cli-configurator is a skill published in the GitHub repository Poorgramer-Zack/copilot-cli-things (2 stars, last pushed 7mo ago), licensed MIT. It adds 79 tokens to every session and 3,183 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
speckit-init
Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running specify init --integration copilot --integration-options="--skills". USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO…
speckit-extension
Manage Spec Kit extensions via specify extension. USE FOR: listing installed extensions as text or JSON, installing/removing/updating extensions, searching the extension catalog, showing extension info, enabling/disabling extensions, setting resolution priority, or managing extension catalogs. DO NOT USE FOR: artifact…
speckit-preset
Manage Spec Kit presets via specify preset. USE FOR: listing installed presets as text or JSON, installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling presets, setting resolution priority, or managing preset catalogs. DO NOT…
speckit-artifact
Inspect the effective Spec Kit artifact inventory and composition stacks via specify artifact. USE FOR: listing commands/templates/scripts/hooks, explaining which preset or extension layer supplies an artifact, inspecting resolution precedence and hidden layers, checking hook registration, or resolving a stack…
speckit-bundle
Discover, install, and author Spec Kit bundles via specify bundle. USE FOR: searching/showing/listing bundles, installing/updating/removing a bundle (a curated set of extensions/presets/integrations/workflows), validating a bundle manifest, building a distributable bundle artifact, initializing a project and…
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…