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 boshi-xixixi/TraeSkill --skill brag-sheetgit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/brag-sheet)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/brag-sheet"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/brag-sheet.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.1 | $0.00200 | $0.02883 |
| Opus 5 | $0.00100 | $0.01442 |
| Sonnet 5 | $0.00040 | $0.00577 |
| Haiku 4.5 | $0.00020 | $0.00288 |
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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- brag-sheet — 94% identical, 17 lines differ
How it starts
The opening of the file, as written. The whole thing — 249 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.
- 7d ago First seen · 249 lines · 200 tokens per session scan A b7c9b04c81fd
brag-sheet is a skill published in the GitHub repository boshi-xixixi/TraeSkill (261 stars, last pushed 3mo ago), licensed MIT. It adds 200 tokens to every session and 2,883 once invoked, about $0.0010 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
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
using-git-worktrees
A guide to using Git worktrees, which let you keep multiple branches in separate folders at the same time.
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.