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.
git clone --depth 1 https://github.com/martineserios/thebranaWrote 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/commands/martineserios/thebrana/repo-cleanup)<a href="https://agentmods.dev/commands/martineserios/thebrana/repo-cleanup"><img src="https://agentmods.dev/badge/commands/martineserios/thebrana/repo-cleanup/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/commands/martineserios/thebrana/repo-cleanup"><img src="https://agentmods.dev/badge/commands/martineserios/thebrana/repo-cleanup.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.00022 | $0.00542 |
| Opus 5.5 | $0.00009 | $0.00217 |
| Sonnet 5.5 | $0.00004 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
repo-cleanup 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
Repo Cleanup
Commit accumulated spec doc changes that have built up across sessions. Follows GitHub Flow: branch, commit, merge, delete.
Process
-
Survey uncommitted changes:
- Run
git statusto see modified and untracked files - Run
git diff --statto see scope of changes per file - For each modified file, run
git diff <file> | head -60to understand what changed
- Run
-
Ensure .gitignore is current:
- Check that tooling artifacts are ignored:
.swarm/,.claude/memory.db,.mcp.json,*.backup.* - If
.gitignoreneeds updating, include that in the first commit
- Check that tooling artifacts are ignored:
-
Group changes by logical batch:
- Changes from the same session or cause should be one commit
- Use
git diff <file>content to infer what session/cause produced each change - Common groupings:
- Doc corrections (manual fixes or from
/brana:reconcilepropagation domain) - New docs (untracked
.mdfiles) - Frontmatter updates (staleness metadata)
- Content updates from
/refresh-knowledge
- Doc corrections (manual fixes or from
- If grouping is unclear, ask the user
-
For each batch:
- Create a branch:
git checkout -b docs/<brief-description> - Stage the relevant files (by name, never
git add -A) - Commit with conventional message:
docs(scope): description - Merge to master:
git merge --no-ff - Delete the branch
- Create a branch:
-
Report:
## Cleanup Complete - N commits across M branches - Files committed: [list] - Files still uncommitted: [list or "none"] - Files ignored: [list of tooling artifacts]
Rules
- Never commit tooling artifacts (
.swarm/,.claude/memory.db,.mcp.json) — these are runtime state, not specs. - Never use
git add -Aorgit add .— always stage by filename. - Ask for clarification whenever you need it. If you can't tell why a file changed or how to group it — ask. Don't guess.
- One logical change per commit. Don't lump unrelated changes together.
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 · 54 lines · 22 tokens per session scan A 619eeb8320a0
repo-cleanup is a command published in the GitHub repository martineserios/thebrana (3 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 542 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-08-31.
Other commands, from other repositories
copush
Pull, version-bump, commit all changes, and push to origin.
replay
You are reconstructing the historical evolution of this sprint by recompiling every version of claims.json from git history.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
genshijin-commit
A command that writes a commit message for changes already placed in Git's staging area. It follows the repository's existing language and uses a short imperative subject without AI attribution.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
amend
Amend last commit safely. Use for amend, fix last commit, update commit, modify commit.