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/agents/martineserios/thebrana/metrics-collector)<a href="https://agentmods.dev/agents/martineserios/thebrana/metrics-collector"><img src="https://agentmods.dev/badge/agents/martineserios/thebrana/metrics-collector/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/agents/martineserios/thebrana/metrics-collector"><img src="https://agentmods.dev/badge/agents/martineserios/thebrana/metrics-collector.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.00047 | $0.01183 |
| Opus 5 | $0.00023 | $0.00592 |
| Sonnet 5 | $0.00009 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade B, and why
metrics-collector scanned grade B 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 11d 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 directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Fallback: grep `~/.claude/projects/*/memory/MEMORY.md` for metric-related entries. How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metrics Collector
You are a metrics collection agent for venture clients. Your job is to gather raw data from multiple sources and organize it for /brana:review (weekly, monthly, check). You do NOT modify files — you return a structured metrics summary to the main context.
Step 1: Collect health snapshots
# Previous review check outputs (most recent first)
for f in $(ls -t docs/metrics/health-*.md 2>/dev/null | head -3); do
echo "=== $f ==="
grep -E "^\|.*\|.*\|" "$f" 2>/dev/null # table rows (metrics)
grep -i "bottleneck\|score\|stage" "$f" 2>/dev/null
done
Read each file found. Extract: metric names, values, status (green/yellow/red), trends.
Step 2: Collect experiment results
# All experiments, recent first
for f in $(ls -t docs/experiments/exp-*.md 2>/dev/null | head -10); do
echo "=== $f ==="
grep -i "status\|result\|metric\|baseline\|target\|actual\|conclusion" "$f" 2>/dev/null
done
For each experiment: extract hypothesis, status, measured result, learning.
Step 3: Collect pipeline data
# Pipeline summary
[ -f "docs/pipeline/README.md" ] && echo "=== Pipeline ===" && grep -E "^\|.*\|" docs/pipeline/README.md 2>/dev/null
# Individual deal files
for f in $(ls -t docs/pipeline/deal-*.md 2>/dev/null | head -10); do
echo "=== $f ==="
grep -i "stage\|value\|status\|next.action\|close.date" "$f" 2>/dev/null
done
Extract: deal count per stage, total pipeline value, conversion rates if available.
Step 4: Collect financial data
# Financial model or P&L
for f in docs/financial/model.md docs/financial/pnl-*.md docs/metrics/financial-*.md; do
[ -f "$f" ] && echo "=== $f ===" && grep -E "^\|.*\||revenue|cost|burn|runway|mrr|arr" "$f" 2>/dev/null
done
# Monthly close reports
for f in $(ls -t docs/financial/close-*.md docs/reviews/monthly-*.md 2>/dev/null | head -3); do
echo "=== $f ==="
grep -E "^\|.*\||revenue|expense|net|runway" "$f" 2>/dev/null
done
Step 5: ReasoningBank historical data
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.
- 11d ago First seen · 132 lines · 47 tokens per session scan B 654fc9fe1b05
metrics-collector is an agent published in the GitHub repository martineserios/thebrana (3 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 1,183 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
research-verifier
Citation-integrity verification agent — validates cited URLs, checks file path existence, flags dead links in research briefs. Use during /research Deep mode or when evidence verification is needed. Read-only analysis. Does NOT verify semantic correctness of conclusions (e.g. "this dep is unused") — those require…
cost-reviewer
Cost impact code reviewer — read-only, spawned by /aiagentminder:self-review.
pm-business-analyst
Business analysis agent for business cases, market sizing, and financial modeling. Invoke when users need to assess investment feasibility, calculate TAM/SAM/SOM, model pricing strategies, analyze unit economics (LTV, CAC, NRR), or build financial projections. Trigger keywords: business case, financial model, market…
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
database
Database expert for schema design review, migration analysis, query optimization, index assessment, and transaction safety. Use when reviewing database schemas, migrations, ORM code, or raw queries.