Copilot Brag Sheet is a GitHub Copilot CLI extension that records coding-session activity, such as edited files, pull requests, and Git operations, in a structured local work-impact log. Developers use it to retain evidence for performance reviews without sending telemetry. The catalogue add-ons provide the extension’s automatic tracking, agent guidance, and MCP integration.
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 microsoft/copilot-brag-sheet --skill brag-sheetgit clone --depth 1 https://github.com/microsoft/copilot-brag-sheetWrote 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/microsoft/copilot-brag-sheet/brag-sheet)<a href="https://agentmods.dev/skills/microsoft/copilot-brag-sheet/brag-sheet"><img src="https://agentmods.dev/badge/skills/microsoft/copilot-brag-sheet/brag-sheet/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/microsoft/copilot-brag-sheet/brag-sheet"><img src="https://agentmods.dev/badge/skills/microsoft/copilot-brag-sheet/brag-sheet.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.00225 | $0.02912 |
| Opus 5.5 | $0.00090 | $0.01165 |
| Sonnet 5.5 | $0.00045 | $0.00582 |
| Haiku 4.5 | $0.00022 | $0.00291 |
Grade A, and why
brag-sheet 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 1mo 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.
This is a copy
94% identical to brag-sheet — 17 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.
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brag Sheet — Work Impact Writer
Turn engineering work into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs, git history, and PRs to reconstruct forgotten work.
USE FOR: "brag", "log work", "what did I do", "backfill", "performance review", "self-review", "promo packet", "weekly update", "status report", "write impact statement", "what did I ship", "I forgot to log my work", "review prep", "accomplishments" DO NOT USE FOR: project management, sprint planning, time tracking, ticket creation
Quick Start
| User wants... | Mode | Output |
|---|---|---|
| Log one accomplishment | Capture | 1 impact-first entry |
| "What did I do last week?" | Backfill | Entries grouped by week, mined from git/PRs/sessions |
| Prep for review or promo | Review Pack | Entries grouped by impact theme + STAR narratives |
Agent Behavior Rules
- DO confirm the time range and scope before scanning sources. Don't assume "last week" — ask.
- DO check which tools are available (
save_to_brag_sheet,git,gh) before choosing a workflow. - DO always include all three parts: action → result → evidence. If evidence is missing, write
(evidence needed)— never silently omit. - DO show drafted entries to the user before saving. Never auto-save without confirmation.
- DO group related commits into a single entry. Ten commits on the same feature = one entry.
- DO preserve the user's voice. Reframe for impact, but don't invent accomplishments or inflate scope.
- DO NOT fabricate metrics, team sizes, or impact numbers. If the user doesn't provide a number, don't invent one.
- DO NOT write entries for work the user only described verbally without verifying. Ask: "Did this ship? Is there a PR or doc I can reference?"
- DO NOT skip the backfill scan steps or draft entries before scanning is complete.
- DO NOT pad weak periods with trivial entries. An honest gap is better than inflated fluff.
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.
- 1mo ago First seen · 250 lines · 225 tokens per session scan A 726099a7622d
brag-sheet is a skill published in the GitHub repository microsoft/copilot-brag-sheet (11 stars, last pushed 3d ago), licensed MIT. It adds 225 tokens to every session and 2,912 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to brag-sheet, differing in 17 lines, and is treated as a copy.
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-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-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-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…