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 agent-developmentgit 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/agent-development)<a href="https://agentmods.dev/skills/poorgramer-zack/copilot-cli-things/agent-development"><img src="https://agentmods.dev/badge/skills/poorgramer-zack/copilot-cli-things/agent-development/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/agent-development"><img src="https://agentmods.dev/badge/skills/poorgramer-zack/copilot-cli-things/agent-development.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.00043 | $0.01982 |
| Opus 5.5 | $0.00017 | $0.00793 |
| Sonnet 5.5 | $0.00009 | $0.00396 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
Agent Development 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.
How it starts
The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Development for Copilot CLI Plugins
Create autonomous agents (.agent.md) that handle complex, multi-step tasks independently. Define structure, triggering conditions, and system prompts.
- Agents are FOR autonomous work, skills are FOR user-initiated actions
- Markdown file format with YAML frontmatter
- Triggering via description field
- System prompt defines agent behavior
- Model customization
Agent File Structure
Complete Format
---
description: Use this agent when [triggering conditions].
model: claude-sonnet-4.5
tools: [read, edit, grep]
---
You are [agent role description]...
**Your Core Responsibilities:**
1. [Responsibility 1]
2. [Responsibility 2]
**Analysis Process:**
[Step-by-step workflow]
**Output Format:**
[What to return]
Frontmatter Fields
description (required)
Defines when Copilot should trigger this agent. This is the most critical field.
Must include:
- Triggering conditions ("Use this agent when...")
- Context describing when agent is appropriate
Format:
Use this agent when [conditions].
Best practices:
- Be specific about triggering conditions
- Cover different phrasings of same intent
- Be specific about when NOT to use the agent
model (optional)
Which model the agent should use.
Options:
claude-sonnet-4.5- Claude Sonnet (balanced, default)claude-opus-4.5- Claude Opus (most capable, expensive)claude-haiku-4.5- Claude Haiku (fast, cheap)
Recommendation: Omit unless agent needs specific model capabilities. Defaults to session model.
tools (optional)
Restrict agent to specific tools.
Format: Array of tool names (lowercase, unquoted)
tools: [read, edit, grep, powershell]
Default: If omitted, agent has access to all tools
Best practice: Limit tools to minimum needed (principle of least privilege)
Common tool sets:
- Read-only analysis:
[read, grep, glob] - Code generation:
[read, edit, grep] - Testing:
[read, powershell, grep] - Full access: Omit field
What ships with it
6 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 · 340 lines · 0 tokens per session scan A 0bc16c85245c
Agent Development is a skill published in the GitHub repository Poorgramer-Zack/copilot-cli-things (2 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 1,982 once invoked, about $0.0002 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.
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…