Borrowing it
Nothing to install: this file belongs to noontide-co/mainbranch. 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/noontide-co/mainbranch/main/.claude/skills/mb-status/SKILL.mdgit clone --depth 1 https://github.com/noontide-co/mainbranchWrote 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/noontide-co/mainbranch/mb-status)<a href="https://agentmods.dev/skills/noontide-co/mainbranch/mb-status"><img src="https://agentmods.dev/badge/skills/noontide-co/mainbranch/mb-status/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/noontide-co/mainbranch/mb-status"><img src="https://agentmods.dev/badge/skills/noontide-co/mainbranch/mb-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.01422 |
| Opus 5 | $0.00019 | $0.00711 |
| Sonnet 5 | $0.00008 | $0.00284 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
mb-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 9d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status
Show the operator the deterministic Main Branch briefing without duplicating repo-health checks in prose.
CLI facts first: Run mb status --json --peek before answering, then use
that JSON as the source of truth.
Shared source: The portable daily start/status workflow contract lives in
workflows/mb-start-status/workflow.md. This Claude skill is the Claude Code
status shell over that source.
Shared contract markers: Keep these aligned with the shared source.
Required commands:
mb status --json --peekmb start --jsonmb doctor repair --plan
mb doctor repair --plan is read-only. If it exits nonzero while returning plan_interpretation and actions, treat that as findings to review, not as an opaque command failure.
Required fact paths:
money_pathmoney_path.policymoney_path.policy.thresholds_declaredmoney_path.active_betsmoney_path.active_bets.unanchoredmoney_path.active_bets.over_capmoney_path.objects.proof.qualityvalidation.file_contractscontent_strategyranked_actionsupdatereadinessreadiness.dimensions.repo_runtimereadiness.dimensions.business_memorydrift.itemsruntime.codex_cliruntime.claude_codesince_last_checkjournalcheckpointonboardingintegrationsgithubtopology.repo_boundarybrain.betsbrain.bets.activebrain.bets.due_soonbrain.bets.overduebrain.bets.exit_criteriabrain.bets.exit_criteria.missingbrain.bets.exit_criteria.triggered_failure_signalsbrain.bets.exit_criteria.triggered_double_down_signalsvocabulary
Approval gates: updates_repairs_migrations, file_writes, checkpoint,
provider_mutation, publishing_or_spend, customer_contact, private_data,
destructive_operations, and status_marker.
Public/private boundaries: no_secrets, no_raw_provider_exports,
no_customer_member_data, no_private_runtime_settings, and
no_raw_finance_legal_records.
Core route: status facts first, runtime mismatch gates before business routing, one owner-facing recommendation, business language first, and explicit approval before mutating the status marker or doing durable writes.
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.
- 9d ago First seen · 158 lines · 39 tokens per session scan A fd5c7561a159
mb-status is a skill published in the GitHub repository noontide-co/mainbranch (39 stars, last pushed 25d ago), licensed MIT. It adds 39 tokens to every session and 1,422 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-30.
Other skills, from other repositories
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).
Meeting Action Extractor
Extract decisions, action items, owners, deadlines, and follow-ups from meeting transcripts — structured output for project tracking.