review

review is a skill for Claude Code from martineserios/thebrana. It costs 35 tokens per session (4,566 once invoked), scanned A, original, MIT.

A business health review for weekly checks, monthly closing, or one-off audits. It examines business context, metrics, revenue, pipeline state, and related records.

In plain words
What is it for?
Use it for weekly reviews, monthly close work, growth checks, and ad-hoc assessments of business performance.
Why use it?
It gives recurring business checks a structured process instead of leaving health assessment scattered across notes and data.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; mentions CLAUDE.md.

Part of the brana plugin — 56 skills, 4 commands, 14 agents, 13 hooks shipped together

Good fit Use it for weekly reviews, monthly close work, growth checks, and ad-hoc assessments of business performance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/martineserios/thebrana/review
Install

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.

Any agent
npx skills add martineserios/thebrana --skill review
Clone the repo
git clone --depth 1 https://github.com/martineserios/thebrana

Made for: Claude Code.

Or install brana, the plugin that ships this one along with the rest of its 56 skills, 4 commands, 14 agents, 13 hooks.

Wrote 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.

agentmods badge for review

README.md
[![agentmods](https://agentmods.dev/badge/skills/martineserios/thebrana/review/github.svg)](https://agentmods.dev/skills/martineserios/thebrana/review)
Your own site
<a href="https://agentmods.dev/skills/martineserios/thebrana/review"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/review/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.

agentmods 80×15 button for review

Your own site · 80×15
<a href="https://agentmods.dev/skills/martineserios/thebrana/review"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,566 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.04566
Opus 5 $0.00017 $0.02283
Sonnet 5 $0.00007 $0.00913
Haiku 4.5 $0.00003 $0.00457

Measured 7d ago against content hash ac2212475d96, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

review 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 7d 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.

system/skills/review/SKILL.md · 400 lines

How it starts

The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review — Business Health

Unified business review skill. Replaces /weekly-review, /monthly-close, /monthly-plan, and /growth-check.

On entry, create a CC Task step registry. Follow the guided-execution protocol.

Register these steps: LOAD, REVIEW (subcommand-specific), EXTRACT, EVALUATE, PERSIST.

ToolSearch("select:mcp__ruflo__memory_search,mcp__ruflo__memory_store")

Step 0 — LOAD

Pull relevant business context into memory before the review. Budget: 30K tokens max.

  1. Build query from available context: "{project} {task.subject} {task.tags joined} {user_input}"
  2. Primary — ruflo MCP (run all in parallel — namespace: "all" only returns session records):
    mcp__ruflo__memory_search(query: "{query} metrics revenue health pipeline", namespace: "knowledge", limit: 2, threshold: 0.4)
    mcp__ruflo__memory_search(query: "{query} metrics revenue health pipeline", namespace: "pattern",   limit: 2, threshold: 0.4)
    mcp__ruflo__memory_search(query: "{query} metrics revenue health pipeline", namespace: "business",  limit: 3, threshold: 0.4)
    
    Merge results, rank by similarity. Focus on: prior review snapshots (namespace: business), pipeline state, event log entries, and health metrics. 2b. Graph edge traversal — see build.md LOAD step 2b. Follow depends_on/informs edges from knowledge results. Max 3 graph-derived docs. Best-effort, never blocks.
  3. Fallback — tag-based grep (if MCP unavailable):
    grep -rl "{keywords}" docs/reviews/ --include="*.md" | head -5
    grep -rl "{keywords}" ~/enter_thebrana/brana-knowledge/dimensions/ --include="*.md" | head -3
    
    Read the most recent review file and top 2 matching dimension files (first 80 lines each).
  4. Skill match handling — if any result has namespace: "skills" and score >= 0.5, mention inline: "Matching skill: /brana:{name} ({score})." Informational only — don't auto-invoke or block. 4a. JIT skill acquisition — if no skills match and topic involves a specific technology, offer marketplace search via Skill(skill="brana:acquire-skills", args="{tech}"). Read installed procedure into context immediately. See build.md LOAD step 4a for full logic and guard rails.
  5. Summarize loaded knowledge as a brief context preamble (2-5 bullets). Surface prior trends, last review's bottleneck, and pipeline status so the review builds on history.

Read the full file on GitHub · 400 lines

Changes

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.

  1. 7d ago First seen · 400 lines · 35 tokens per session scan A ac2212475d96

Subscribe to this mod's changes

review is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 4,566 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.

Related

Other skills, from other repositories

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…

wondelai/skills · 147 tokens

team-topologies

Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or…

wondelai/skills · 155 tokens

telemetry-inspect

Inspects the OrchestKit telemetry pipeline for the current project — lists all known telemetry files with write counts, sizes, schema status, growth trend, and orphan detection. Use when verifying the observability pipeline is healthy, debugging a missing writer, or auditing which files have schema locks vs. which are…

yonatangross/orchestkit · 78 tokens

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.

cryndoc/polisade-orchestrator · 127 tokens

continue

Autonomous work — find and execute ready tasks.

cryndoc/polisade-orchestrator · 11 tokens

roadmap

An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.

cryndoc/polisade-orchestrator · 109 tokens