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/martineserios/thebrana/docsnpx skills add martineserios/thebrana --skill docsgit 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/docs)<a href="https://agentmods.dev/skills/martineserios/thebrana/docs"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/docs.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 | $0.00027 | $0.02421 |
| Opus 5 | $0.00014 | $0.01210 |
| Sonnet 5 | $0.00005 | $0.00484 |
| Haiku 4.5 | $0.00003 | $0.00242 |
Grade A, and why
docs 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Living Documentation
Generate and update project documentation from build context. Works standalone or as a building block invoked by other skills (CLOSE, reconcile).
When to use
- After building a feature — generate tech doc + user guide
- After
/brana:buildCLOSE step — invoked automatically viaall - Manually — update philosophy, regenerate stale docs, or fill doc gaps
- From other skills — any skill can invoke
/brana:docsfor its doc needs
Subcommands
/brana:docs tech [task-id] — generate/update tech doc for a feature
/brana:docs guide [task-id] — generate/update user guide for a feature
/brana:docs overview — update philosophy.md with latest patterns
/brana:docs all [task-id] — run tech + guide + shared doc updates + overview
/brana:docs tech
Generate or update a technical architecture doc for a feature.
Input sources
Gather context from (in priority order):
- Task metadata (if task-id provided):
backlog_get(task_id: "{task-id}")(MCP) orbrana backlog get {task-id}— subject, description, context, strategy, tags - Git diff:
git diff main...HEAD --stat— what files changed - Feature spec: check
docs/architecture/features/for existing spec matching the task slug - Design decisions: from task context field and any ADRs created during the build
Output
Write to docs/architecture/features/{feature-slug}.md with these sections:
| Section | Contents |
|---|---|
## Goal |
What the feature does and the problem it solves |
## Design Decisions |
Choices made and why, linking any ADRs |
## Code Flow |
Entry points and the path through the code |
## Testing |
What is covered, and how to run it |
Steps
- Gather input sources (parallel where possible)
- If a tech doc already exists for this feature:
- Read it
- Show diff preview of proposed changes
- Ask: "Update existing doc?" via AskUserQuestion — options: "Show diff preview (Recommended)", "Apply changes directly"
- If no doc exists:
- Fill template from gathered context
- Write the file
- Report: "Tech doc written:
docs/architecture/features/{slug}.md"
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 · 279 lines · 27 tokens per session scan A 813c303357eb
docs is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 2,421 once invoked, about $0.0001 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
architecture-decision-record
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
document-writer
Write or update technical documentation grounded in the real codebase. Use when the user asks for README, API docs, architecture guides, user guides, CONTRIBUTING docs, migration notes, or JSDoc/code comments, or wants technical docs rewritten into natural Chinese with correct terminology. Not for general prose…
help
Use when asked what the capstone plugin can do - prints the usage block.
core
Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.
groom
Use when starting work on a feature or change for a project that already has capstone docs - "new feature", "add a feature", "implement X", "build X", "design a feature", "spec it out", "flesh out", "refine this idea", "let's work on X" - a doc-grounded one-question-at-a-time interview producing a traceable feature…
map
Use when asked to build, refresh, update, or check a codebase's architecture reference docs - "map the codebase", "document this repo", "are the docs current", "bring the docs in line with the code" - writes a docs/capstone/ index plus topic chapters, the logic/ business-logic map and the uiux/ surface map, then on…