status

A command that lists current and past Copilot jobs for a code repository, including their review status and progress details.

In plain words
What is it for?
Use it to monitor Copilot coding or review jobs, or to inspect the complete output for one job when you provide its ID.
Why use it?
It gives you one compact view of work that is running or has recently finished, so you do not have to check each job separately.

Command

Install

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.

agentmods
npx agentmods add commands/wagnersza/copilot-plugin-cc/status
Clone the repo
git clone --depth 1 https://github.com/wagnersza/copilot-plugin-cc
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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 $0.00016 $0.00189
Opus 5 $0.00008 $0.00095
Sonnet 5 $0.00003 $0.00038
Haiku 4.5 $0.00002 $0.00019

Measured 2d ago against content hash 7def1eab1a17, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

Origin

This is a copy

92% identical to status — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/copilot/commands/status.md · 18 lines

What it actually says

!node "${CLAUDE_PLUGIN_ROOT}/scripts/copilot-companion.mjs" status $ARGUMENTS

If the user did not pass a job ID:

  • Render the command output as a single Markdown table for the current and past runs in this session.
  • Keep it compact. Do not include progress blocks or extra prose outside the table.
  • Preserve the actionable fields from the command output, including job ID, kind, status, phase, elapsed or duration, summary, and follow-up commands.

If the user did pass a job ID:

  • Present the full command output to the user.
  • Do not summarize or condense it.
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. 2d ago First seen · 18 lines · 16 tokens per session scan A 7def1eab1a17

Subscribe to this mod's changes

status is a command published in the GitHub repository wagnersza/copilot-plugin-cc (45 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 189 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to status, differing in 4 lines, and is treated as a copy.