Borrowing it
Nothing to install: this file belongs to ezBuilder/code-brain. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ezBuilder/code-brain/main/.agents/skills/source-command-cb-upgrade/SKILL.mdgit clone --depth 1 https://github.com/ezBuilder/code-brainWrote 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/ezbuilder/code-brain/source-command-cb-upgrade)<a href="https://agentmods.dev/skills/ezbuilder/code-brain/source-command-cb-upgrade"><img src="https://agentmods.dev/badge/skills/ezbuilder/code-brain/source-command-cb-upgrade/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/ezbuilder/code-brain/source-command-cb-upgrade"><img src="https://agentmods.dev/badge/skills/ezbuilder/code-brain/source-command-cb-upgrade.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.00024 | $0.00185 |
| Opus 5.5 | $0.00010 | $0.00074 |
| Sonnet 5.5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
source-command-cb-upgrade 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 2mo 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.
What it actually says
source-command-cb-upgrade
Use this skill when the user asks to run the migrated source command cb-upgrade.
Command Template
.ai/bin/ai upgrade latest --json 실행. 네트워크와 파일 갱신을 수행하는 명시적 명령이다. 성공 후 새 Claude/Codex/Antigravity 세션을 열어야 새 규칙이 적용된다.
출력 규칙:
ok=true:코드브레인 업그레이드 완료 — 새 세션 필요ok=false:코드브레인 업그레이드 실패 — {error}- 표·박스·이모지·코드블록·추가 해설 금지.
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.
- 2mo ago First seen · 18 lines · 24 tokens per session scan A 6607646dca6e
source-command-cb-upgrade is a skill published in the GitHub repository ezBuilder/code-brain (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 185 once invoked, about $0.0001 per session on Opus 5.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
release-checker
Use before claiming tests pass, a build succeeds, a bug is fixed, requirements are met, or a release/PR is ready to ship. Demands fresh verification evidence instead of assumptions, confidence, or previous runs.
conventional-git
Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases…
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.
branch_health
Quick health check -- test counts and file stats for AIPass branches.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
github-ops
GitHub remote operations and README authoring: repo creation, metadata, releases, issue/PR management with preview-before-send, README as a landing page (badge row, features-as-benefits, screenshots, Recent Updates), and read-only security auditing. Triggers on: write a README, improve the README, README badges…