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-endnpx skills add noontide-co/mainbranch --skill mb-endgit clone --depth 1 https://github.com/noontide-co/mainbranchWhat 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 | $0.00113 | $0.04823 |
| Opus 5 | $0.00056 | $0.02412 |
| Sonnet 5 | $0.00023 | $0.00965 |
| Haiku 4.5 | $0.00011 | $0.00482 |
Grade A, and why
mb-end 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 yesterday.
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 — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End
Close your session intentionally. The bookend to /mb-start.
You only run this when you choose to. It is never auto-invoked.
Shared source: The portable workflow contract lives in
workflows/mb-end/workflow.md. This Claude skill is the Claude Code shell over
that source.
CLI facts first: After finding the business repo, run
mb status --json --peek and mb checkpoint --plan --json before summarizing
the session or offering to save. Use status journal, since_last_check,
dirty-work, readiness, and checkpoint facts as the primary source. Raw git is
fallback/detail only when mb facts are unavailable or a crystallize step needs
site-code history the CLI does not expose.
Shared contract markers: Keep these aligned with the shared source.
Required commands:
mb status --json --peekmb start --jsonmb doctor repair --planmb checkpoint --plan --jsonmb validate --json
Required fact paths:
money_pathmoney_path.objects.proof.qualityvalidation.file_contractscontent_strategyranked_actionsupdatereadinessdrift.itemsruntime.codex_cliruntime.claude_codejournalsince_last_checkcheckpoint.pendingcheckpoint.pending.changed_filescheckpoint.pending.blockerscheckpoint.pending.proposed_subjectsummary.changed_filessafety.blocksproposal.messagevalidation
Approval gates: updates_repairs_migrations, file_writes, checkpoint,
provider_mutation, publishing_or_spend, customer_contact, private_data,
destructive_operations, and public_issue_or_proposal.
Public/private boundaries: no_secrets, no_raw_provider_exports,
no_raw_transcripts, no_customer_member_data,
no_private_runtime_settings, and no_raw_finance_legal_records.
Core closeout flow: status scan, checkpoint plan, session summary, final thought capture, crystallize, approval-gated save, owner-facing save states, and warm close.
Philosophy
The end of a session is the highest-leverage reconnection point. All session you were doing -- researching, deciding, generating. Now you step back and see what actually happened. Accumulated doing becomes conscious understanding.
What ships with it
2 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.
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.
- yesterday First seen · 474 lines · 113 tokens per session scan A a8fb7ca61183
mb-end is a skill published in the GitHub repository noontide-co/mainbranch (37 stars, last pushed 17d ago), licensed MIT. It adds 113 tokens to every session and 4,823 once invoked, about $0.0006 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
review-pr
Review a Dograh pull request, branch diff, or pasted patch for repo-specific security and correctness risks that are not obvious from generic FastAPI, Next.js, or Python conventions. Use when the user asks to review a PR, audit a diff, check whether changes are safe to merge, review their own changes, or asks what to…
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.
cli-commands
MUST use when using the CLI, including debugging job failures and inspecting run history via wmill job.
native-trigger
Guidance for adding native trigger services to Windmill. Use when implementing or modifying native trigger integrations across the backend and frontend.
write-script-python3
MUST use when writing Python scripts.
write-workflow-as-code
MUST use when writing or modifying Windmill Workflow-as-Code scripts using workflow, task, step, sleep, approvals, taskScript, taskFlow, taskscript, or taskflow.