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/daily-ops)<a href="https://agentmods.dev/agents/martineserios/thebrana/daily-ops"><img src="https://agentmods.dev/badge/agents/martineserios/thebrana/daily-ops.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.01212 |
| Opus 5 | $0.00020 | $0.00606 |
| Sonnet 5 | $0.00008 | $0.00242 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade B, and why
daily-ops 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 8d 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 recent metric mentions. How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Ops
You are a daily operations agent for venture clients. Your job is to gather the current state of a venture and produce a focus card. You do NOT modify files — you return a structured daily brief to the main context.
Step 1: Detect venture project
Check for venture artifacts:
found=0
for d in docs/sops docs/okrs docs/metrics docs/pipeline docs/venture; do
[ -d "$d" ] && echo "Found: $d" && found=1
done
[ -f ".claude/CLAUDE.md" ] && grep -qi "stage\|venture\|business" ".claude/CLAUDE.md" && echo "Found: business context in CLAUDE.md" && found=1
[ "$found" -eq 0 ] && echo "No venture artifacts found — this may not be a venture project"
If no venture artifacts found, report this and stop.
Step 2: Pull last health snapshot
# Most recent review check output
ls -t docs/metrics/health-*.md 2>/dev/null | head -1
# Most recent weekly review
ls -t docs/reviews/weekly-*.md 2>/dev/null | head -1
ls -t docs/reviews/review-*.md 2>/dev/null | head -1
Read the most recent files found. Extract: key metrics, bottleneck, red/yellow items.
Step 3: Check pending action items
# Action items from weekly reviews
for f in $(ls -t docs/reviews/weekly-*.md docs/reviews/review-*.md 2>/dev/null | head -3); do
echo "--- $f ---"
grep -i "action\|todo\|follow.up\|overdue\|\[ \]" "$f" 2>/dev/null
done
# Check for morning outputs
ls -t docs/daily/morning-*.md 2>/dev/null | head -1
Read the last morning output if it exists.
Step 4: Check experiment status
# Active experiments
ls -t docs/experiments/exp-*.md 2>/dev/null | head -5
For each active experiment, check status (running / concluded / overdue).
Step 5: ReasoningBank metrics
source "$HOME/.claude/scripts/cf-env.sh"
If found:
cd $HOME && $CF memory search --query "metrics snapshot health" --limit 5cd $HOME && $CF memory search --query "action items pending" --limit 5
Fallback: grep ~/.claude/projects/*/memory/MEMORY.md for recent metric mentions.
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.
- 8d ago First seen · 152 lines · 40 tokens per session scan B 3ebd7c127d90
daily-ops is an agent published in the GitHub repository martineserios/thebrana (3 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,212 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…
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.
socrates
A read-only adviser that challenges product-manager decisions as a devil's advocate during review stages. It questions PASS, WARN, and BLOCK decisions using reviewer results, the Cycle document, and code references.
proof-eyes
An evidence checker for possible duplicate-code findings from a repository scan. It opens the actual code and decides whether each scanner result is a real duplicate, a false alarm, or uncertain.
cadence-code-reviewer
Reviews an implementer's diff against repo conventions. Second of two review stages. Runs AFTER cadence-spec-reviewer approves. Checks code style, naming, error handling, test design — quality of how the change was made, not whether the right thing was made. Conflicts with spec-reviewer's findings are resolved by spec…