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 martineserios/thebrana --skill dogit 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/skills/martineserios/thebrana/do)<a href="https://agentmods.dev/skills/martineserios/thebrana/do"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/do.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.00040 | $0.00368 |
| Opus 5 | $0.00020 | $0.00184 |
| Sonnet 5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
do 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 4d 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
Do — Alias for backlog start
/brana:do is an alias for /brana:backlog start with freeform text input.
For the ordered idea → ship walkthrough this alias enters at, see Idea → Ship: The Skill Flow — start there when the question is "which skill for this," not just "start this task."
Usage
/brana:do <description>
How it works
Invoke /brana:backlog start with the arguments treated as freeform text (step 1a of the start procedure):
Skill(skill="brana:backlog", args="start $ARGUMENTS")
All routing, skill matching, task creation, and batch detection logic lives in /brana:backlog start. See system/skills/backlog/phases/start.md § /brana:backlog start → step 1a.
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.
- 4d ago First seen · 39 lines · 40 tokens per session scan A 5f5f5426229a
do is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 368 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
status
A progress-reporting command that reads phase logs from a project and displays a summary in English or Korean.
pr-review-watcher
Monitors for incoming PR reviews and summarizes their content. Determines approval/change-request/comment verdicts and extracts action items. Triggers on "did the PR review come in?", "when will the review arrive", "PR waiting" utterances.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
continue
Autonomous work — find and execute ready tasks.
prd
A Product Requirements Document (PRD) writer for large software initiatives. A PRD records the problem, goals, requirements, assumptions, and evidence before implementation begins.
roadmap
An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.