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/drvoss/everything-copilot-cli/skill-creatornpx skills add drvoss/everything-copilot-cli --skill skill-creatorgit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWhat 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.00041 | $0.02910 |
| Opus 5 | $0.00020 | $0.01455 |
| Sonnet 5 | $0.00008 | $0.00582 |
| Haiku 4.5 | $0.00004 | $0.00291 |
Grade A, and why
skill-creator 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 2d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
A meta-skill that produces new SKILL.md files. Describe what the skill should do, and this skill generates a complete, convention-compliant SKILL.md file ready to commit.
When to Use
- You want to add a new skill but are unsure of the required structure
- You have a workflow in mind and want to formalize it as a skill
- You are migrating a skill from another source and need to adapt it to this repo's format
- You need to translate an external slash-command or Claude-oriented pattern into Copilot-native primitives
- Bootstrapping multiple skills quickly for a new domain
When NOT to Use
| Instead of skill-creator | Use |
|---|---|
| Editing an existing skill | edit tool directly |
| Creating an agent definition | See agents/ directory conventions in AGENTS.md |
| Writing an orchestration pattern | See orchestration/patterns/ |
Prerequisites
- A clear description of the workflow the skill should encode
- Knowledge of which
skills/subdirectory it belongs to:development/— coding, debugging, testing workflowssecurity/— security scanning, review, hardeningtesting/— test strategy, eval, coveragedocumentation/— doc generation, update workflowscontent/— copywriting, SEO, content strategyproduct/— PRD, launch, roadmapworkflow/— process workflows (research, release, sprint)copilot-exclusive/— GitHub Copilot CLI-specific features
- Confirm the category already exists in this repository. Research-focused skills
currently live under
workflow/; adding a new category requires updating the shared allowlist inscripts/skill-metadata.jsbefore introducing new files.
Workflow
1. Gather requirements
Ask (or determine from context):
1. What is the skill name? (kebab-case, e.g., `api-versioning-guide`)
2. What category does it belong to? (development / security / testing / etc.)
3. What triggers this skill? (When should an agent use it?)
4. What is the step-by-step workflow?
5. What are the verification criteria (Done When)?
6. Are there any anti-patterns or common mistakes to warn about?
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.
- 2d ago First seen · 318 lines · 41 tokens per session scan A a53d37fa1b5e
skill-creator is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 6d ago), licensed MIT. It adds 41 tokens to every session and 2,910 once invoked, about $0.0002 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
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.
rig
Minimal agent cli harness for defining harnesses in prompts as rig markdown fences.
atifact
This skill should be used when the user asks to "extract agent trajectory", "convert HAR to trajectory", "get trajectory from session", "parse agent session", "convert Claude Code logs", "convert Copilot CLI logs", "extract ATIF", or needs to convert HAR files or JSONL session logs into ATIF trajectory JSON using the…
update-skill-with-log
允许 organizer 和 player 调整 skill，但每次变更都必须同步做文档记录。.
explain-project-design
把这个仓库解释成一个从 coordinator-heavy live loop 演进到 standalone bridge 的版本化多智能体设计。.
ai-ready
ANALYSIS SKILL — Analyze any repository and generate AI-ready configuration — AGENTS.md, copilot-instructions.md, skills, CI workflows, issue templates. WHEN: "make this repo ai-ready", "set up AI config", "add copilot instructions", "prepare this repo for AI contributions", "generate AGENTS.md". INVOKES: glob, grep…