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 agentmods add skills/noontide-co/mainbranch/mb-setupnpx skills add noontide-co/mainbranch --skill mb-setupgit 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-setup)<a href="https://agentmods.dev/skills/noontide-co/mainbranch/mb-setup"><img src="https://agentmods.dev/badge/skills/noontide-co/mainbranch/mb-setup.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.00142 | $0.05401 |
| Opus 5 | $0.00071 | $0.02701 |
| Sonnet 5 | $0.00028 | $0.01080 |
| Haiku 4.5 | $0.00014 | $0.00540 |
Grade A, and why
mb-setup scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> curl -o ~/.whisper/ggml-base.en.bin -L \ 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.
Repo Setup
Get a new user fully configured with Claude Code and their business repo. Use
shipped mb commands for setup facts before teaching concepts or reading
reference prose.
CLI facts first: Run mb doctor, mb start --json, and
mb status --json --peek when a repo exists or can be identified. Use
mb onboard status --json as the read-only progress check for existing repos.
Use mb onboard plan only after the operator approves writing setup progress;
do not keep onboarding state only in chat prose. If there is no repo yet,
inspect mb onboard --help, explain the target folder, ask for approval, then
use mb onboard to create one instead of hand-rolling repo-shape checks.
For provider setup, use mb connect plan and mb connect doctor --json as the
durable readiness contract. Explain providers as business capabilities, not
developer config, and end with exact commands.
Pasted setup guide = setup intent. If the user pastes this guide, the
beginner setup guide, the README "Set up with AI" prompt ("I want Main
Branch: AI business memory I own as files..."), or any bootstrap prompt with
business/folder intent, treat it as setup intent, not as a document to save.
Do not offer to save it as a document. Check mb --version; if missing, stop
with pipx install mainbranch. If present, inspect mb onboard --help,
explain the target folder, and ask before any write. When the pasted prompt
carries its own arc (brief interview, then install → doctor → onboard → seed
core files → teach the daily loop), follow that arc: interview first, stop at
the named first win, and show what was set up.
GitHub-backed setup preflight. GitHub is strongly recommended because it
gives Main Branch a free cloud backup, shared history, task/proposal layer, and
connector-friendly copy of the business brain. Main Branch can start locally
without GitHub. If the user wants backup, sync, collaboration, or mb onboard --github <owner/repo> --push, check gh auth status and
gh api user --jq .login first.
Confirm the account is the one they expect before running a writing setup
command.
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/claude-md-guide.md 5.0 KB
- references/context-gathering.md 4.8 KB
- references/cwd-detection.md 3.8 KB
- references/engine-path-resolution.md 4.8 KB
- references/file-education.md 4.4 KB
- references/git-workflow.md 4.1 KB
- references/migration-multi-offer.md 2.5 KB
- references/nano-banana-setup.md 4.5 KB
- references/repo-scaffolding.md 4.6 KB
- references/repo-visibility-rubric.md 2.8 KB
- references/templates.md 15 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.
- 6d ago First seen · 501 lines · 142 tokens per session scan A e2488eaa2192
mb-setup is a skill published in the GitHub repository noontide-co/mainbranch (38 stars, last pushed 22d ago), licensed MIT. It adds 142 tokens to every session and 5,401 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
shieldcn-badges
Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero sections. Use when a user wants shadcn/ui-styled badges, Shields.io replacement, npm/GitHub/CI/status badges, download charts, README header banners, contributor/sponsor images, or README Studio guidance.…
soul-grader
Use when grading, reviewing, rewriting, or approving a Hermes Agent SOUL.md. Uses the SOUL.md field-guide research artifacts as the only normative source for what makes a good SOUL.md.
anakinscraper
Scrape any website into clean markdown or structured JSON. Anti-detect browser, smart proxy rotation, AI-powered data extraction.
robel-auth
Integrate and maintain Robelest Convex Auth in apps by always checking upstream before implementation. Use when adding auth setup, updating auth wiring, migrating between upstream patterns, or troubleshooting @robelest/convex-auth behavior across projects.
write
Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…