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/wkin-t/claude-copilot-plugin/copilot-runtimenpx skills add wkin-t/claude-copilot-plugin --skill copilot-runtimegit clone --depth 1 https://github.com/wkin-t/claude-copilot-pluginWrote 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/wkin-t/claude-copilot-plugin/copilot-runtime)<a href="https://agentmods.dev/skills/wkin-t/claude-copilot-plugin/copilot-runtime"><img src="https://agentmods.dev/badge/skills/wkin-t/claude-copilot-plugin/copilot-runtime.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.00039 | $0.00708 |
| Opus 5 | $0.00019 | $0.00354 |
| Sonnet 5 | $0.00008 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
copilot-runtime 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot CLI Runtime
Use this skill only inside copilot-cli:copilot-task and copilot-cli:copilot-review subagents.
Invocation Template
Always use a temporary file to pass the prompt — this avoids shell injection when file contents are embedded.
Run the Bash call with run_in_background: true, then immediately use Monitor to stream the result. Never use sleep, until loops, or output-file polling to wait for completion.
_prompt_file=$(mktemp /tmp/copilot-prompt-XXXXXX.txt)
cat > "$_prompt_file" << 'PROMPT_EOF'
<task_prompt>
PROMPT_EOF
copilot -p "$(cat "$_prompt_file")" \
--model <model> \
[--effort <effort>] \
-s \
--allow-all \
[--add-dir <working_dir>]
rm -f "$_prompt_file"
With -s (silent), copilot emits output only once at completion — Monitor fires exactly when the result is ready, with no wasted polling rounds.
Required Flags
| Flag | Purpose |
|---|---|
-s / --silent |
Only output model response, suppress stats |
--allow-all |
Grant all permissions for non-interactive mode. Grants Copilot CLI full tool access — do not use in untrusted environments |
Model Routing
| Model | Used by | Strengths |
|---|---|---|
claude-sonnet-4-6 |
copilot-task (fixed) |
Context-heavy delegation, exploration, architecture |
gpt-5.4 |
copilot-review (fixed) |
Edge cases, boundary conditions, adversarial review |
gpt-5-mini |
Debug only — never for real tasks | Plugin testing |
Agents hard-code their model choice; do not override. Default --effort high for all real tasks.
Context Injection
⚠️ Privacy notice: Copilot CLI auto-loads
./CLAUDE.mdand./.claude/CLAUDE.mdfrom the working directory and sends them to GitHub Copilot (Microsoft/OpenAI servers). If your CLAUDE.md contains internal system prompts, proprietary constraints, or sensitive business context, run from a clean directory or ensure your CLAUDE.md is safe to share externally.
For additional context (memory, file contents): embed directly in the prompt inside <context> tags.
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.
- 4d ago First seen · 73 lines · 39 tokens per session scan A ccb6c030b0cf
copilot-runtime is a skill published in the GitHub repository wkin-t/claude-copilot-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 708 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…