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 skills add brain-bootstrap/claude-code-brain-bootstrap --skill mrgit clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapWrote 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/brain-bootstrap/claude-code-brain-bootstrap/mr)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/mr"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/mr/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/brain-bootstrap/claude-code-brain-bootstrap/mr"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/mr.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.00035 | $0.00428 |
| Opus 5.5 | $0.00014 | $0.00171 |
| Sonnet 5.5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
mr 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 1mo 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
MR/PR Description Skill
Generate a structured pull request description.
Prerequisites
/reviewMUST pass (verdict: PASS, confidence ≥ 95) before generating a PR description- All tests must be green
- No blocking issues from the review
Protocol
1. Verify prerequisites
# Confirm tests pass
# (use the test command from claude/build.md)
If tests fail: STOP. Fix before generating the PR description.
2. Read the PR template
Read claude/templates.md — the required PR/MR format for this project.
3. Gather the diff
git --no-pager diff main...HEAD --stat | head -50
git --no-pager log main...HEAD --oneline | head -20
4. Read the linked ticket (if any)
If a ticket number is referenced, extract the requirements from it.
5. Generate the PR description
Use the template from claude/templates.md. If no template exists, use this default:
## What
<One paragraph: what does this change do and why?>
## Why
<One paragraph: what problem does this solve? Link to ticket.>
## How
<Bullet list: key implementation decisions and approach>
## Testing
<What was tested? How? Test commands run + results>
## Checklist
- [ ] Tests pass
- [ ] No new warnings
- [ ] Documentation updated (if applicable)
- [ ] Breaking changes documented (if applicable)
6. Present to user
Show the PR description and proposed git push command. Wait for confirmation before pushing.
Rules
- NEVER generate a PR description before review passes
- NEVER include implementation details that would confuse reviewers
- NEVER push without explicit user confirmation
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.
- 1mo ago First seen · 67 lines · 35 tokens per session scan A 5335045c4aed
mr is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 428 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-09-03.
Other skills, from other repositories
review-code
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
merge-docs
Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.