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-start/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-start)<a href="https://agentmods.dev/skills/noontide-co/mainbranch/mb-start"><img src="https://agentmods.dev/badge/skills/noontide-co/mainbranch/mb-start/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-start"><img src="https://agentmods.dev/badge/skills/noontide-co/mainbranch/mb-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 155 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 253 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00076 | $0.05266 |
| Opus 5 | $0.00038 | $0.02633 |
| Sonnet 5 | $0.00015 | $0.01053 |
| Haiku 4.5 | $0.00008 | $0.00527 |
Grade A, and why
mb-start 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 — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start
Single entry point: detect business state, intent, save/sync posture, and the smallest useful next route.
Router and language contract
This skill routes; it is not the worker for coordinated output. Use
references/router-and-language.md as the
business router before presenting a menu.
Business language comes first. Say saved checkpoint, unsaved local work, catch
up, sync, reconcile, shared repo, workspace, and provider readiness. Keep raw
git terms, checkpoint ids, branch names, origin, ahead, behind, rebase,
and commit out of the first response unless the user asks for technical detail
or the exact command must be shown.
When summarizing repo state, count pushes/ records, flag campaigns/ as
legacy only, and use core/vocabulary.md display words (real paths in commands).
CLI facts first: Once the business repo path is known, run
mb status --json --peek before asking setup or routing questions. Treat JSON
as source of truth for update severity, readiness, drift, onboarding,
integrations, GitHub, team, bets, dirty git, since-last-check,
content_strategy, money_path, validation.file_contracts, and
ranked_actions. Use GitHub author_display/author_known when naming
people. Parse the full JSON once; do not slice status output with head or
sed.
Shared source: The portable daily start/status workflow contract lives
in workflows/mb-start-status/workflow.md; this skill is its Claude shell.
Shared contract markers: Keep these aligned with the shared source.
Required commands:
mb status --json --peekmb start --jsonmb doctor repair --planRequired 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_signalsvocabularyApproval gates:updates_repairs_migrations,file_writes,checkpoint,provider_mutation,publishing_or_spend,customer_contact,private_data,destructive_operations, andstatus_marker.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/auto-heal.md 5.5 KB
- references/config-system.md 13 KB
- references/launch-orchestration.md 3.8 KB
- references/mcp-preflight.md 5.2 KB
- references/pull-engine-updates.md 1.4 KB
- references/readiness-assessment.md 34 KB
- references/repo-detection.md 7.0 KB
- references/router-and-language.md 14 KB
- references/tool-status-audit.md 1.3 KB
- references/triage-agent.md 27 KB
- references/triage-menu.md 4.6 KB
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 · 501 lines · 76 tokens per session scan A 1847b7a2b2f9
mb-start is a skill published in the GitHub repository noontide-co/mainbranch (39 stars, last pushed 25d ago), licensed MIT. It adds 76 tokens to every session and 5,266 once invoked, about $0.0004 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.