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 reconcilegit 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/reconcile)<a href="https://agentmods.dev/skills/martineserios/thebrana/reconcile"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/reconcile/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/martineserios/thebrana/reconcile"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/reconcile.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.00030 | $0.03451 |
| Opus 5 | $0.00015 | $0.01725 |
| Sonnet 5 | $0.00006 | $0.00690 |
| Haiku 4.5 | $0.00003 | $0.00345 |
Grade A, and why
reconcile scanned grade A with 1 finding 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 2d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat > ~/.claude/run-state/active-goal.json <<JSON Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reconcile
Unified maintenance command for the brana system. Four domains, one entry point.
| Domain | Scope flag | What it checks |
|---|---|---|
| Consistency | --scope consistency |
Spec docs vs system/ implementation drift; CONTEXT.md vs docs/domain/ (default) |
| Security | --scope security |
Secrets, permissions, MCP tax, dangerous settings, credential files, acquired skill safety |
| Propagation | --scope propagation |
Doc fitness checks, reflection gaps, spec-graph consistency, dim "Could Adopt" → backlog scan |
| Knowledge | --scope knowledge |
Stale dimensions, event log bloat, ruflo noise (DECAY) |
--scope all runs every domain sequentially.
Sibling note (ADR-056): the close skill's Step 8b PROPAGATE is a different surface despite the similar name — it audits promise-fulfillment and state-contradiction debt (unchecked Documentation Plan items, stale Status fields, contradicted memories) at close time. This
propagationscope cascades errata and validates the spec graph on demand. Neither replaces the other.
Replaces: /brana:audit (merged into security domain).
Usage
/brana:reconcile — consistency (default, backward compatible)
/brana:reconcile --scope security — security checks only
/brana:reconcile --scope propagation — spec cascade + graph checks
/brana:reconcile --scope knowledge — knowledge hygiene (DECAY)
/brana:reconcile --scope all — run all domains
Parse --scope from $ARGUMENTS. If no --scope flag is present, default to consistency.
Phase Protocol — how to execute this skill
The domain procedures live in per-phase files under phases/ (this skill's base directory). Never execute a scope from memory. Three rules:
- On invocation: resolve the scope from
$ARGUMENTS, then Read its phase file from the PHASES registry below BEFORE doing any of its work. A phase you have not Read this session does not exist — do not improvise its steps. --scope all: Read each domain's phase file as that domain begins — consistency → security → propagation → knowledge, one Read per boundary, not all upfront.- On resume after compression: identify the active scope and step (CC TaskList
/brana:reconcile — {STEP}entries), then Read that scope's phase file before continuing. Previously loaded phase content did NOT survive compression.
What ships with it
4 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.
- 2d ago Changed · +8 lines 0129e45515a0
- 6d ago First seen · 205 lines · 30 tokens per session scan A ca2c57cdc4b1
reconcile is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 3,451 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
project-execution
Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.
kotter-change-model
Guides organizational change initiatives using Kotter's eight-step model: creating urgency, forming a guiding coalition, developing a vision, communicating the vision, empowering action, generating short-term wins, consolidating gains, and anchoring changes in culture. Use when leading a strategic pivot, implementing…
docs-audit
A scheduled review that looks for documentation that may no longer match recently changed source code. It examines Git history and searches documentation for references to changed files or names.
harness
Use when governing a workspace's control plane, code or not — the 01-TOOLS/ tooling layer, the 02-DOCS/ chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy XX- folders, scaffolds provider tooling, sweeps the inbox, writes root CLAUDE.md/AGENTS.md. NOT the bootstrap front door (that is init, which…
hatch3r-issue-workflow
Guides the 8-step agentic development workflow for issues/work items. Covers parsing issues, loading skills, reading specs, planning, implementing, testing, opening PRs/MRs, and addressing review. Use when working on any issue/work item or when the user mentions an issue number.
hatch3r-pr-creation
Creates a pull request or merge request following project conventions including branch naming, PR/MR template, checklist, and rollout plan. Use when opening or preparing a PR/MR, or when the user asks to create a PR or MR.