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/commands/martineserios/thebrana/triage_stale.spec)<a href="https://agentmods.dev/commands/martineserios/thebrana/triage_stale.spec"><img src="https://agentmods.dev/badge/commands/martineserios/thebrana/triage_stale.spec/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/commands/martineserios/thebrana/triage_stale.spec"><img src="https://agentmods.dev/badge/commands/martineserios/thebrana/triage_stale.spec.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.00000 | $0.00447 |
| Opus 5 | $0.00000 | $0.00224 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
triage_stale.spec 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 10d 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.
What it actually says
triage-stale spec stub
Task: t-1355
Command: brana backlog triage-stale
Problem
402+ pending tasks exist. ~24 have feat/fix/merge commits on main — they were shipped but never closed. Manual reconciliation is impractical.
Behaviour
- Run
git log --all --onelinein the repo root - Extract task IDs from branch-name patterns in merge commits and direct commits (precision match — branch prefix only, not casual mentions)
- Cross-reference against pending tasks in tasks.json
- Present matches in batches of N (default 10) and prompt: close / skip / quit
- Close confirmed tasks (status → completed, completed date → today)
Precision match patterns
A task ID t-NNN counts as "shipped" if it appears in git log as:
- A merge commit subject:
merge(feat/t-NNN-...),merge(fix/t-NNN-...),merge(refactor/t-NNN-...) - A branch-name-prefixed direct commit: subject starts with
feat(t-NNNorfix(t-NNN— i.e. the scope IS the task ID
Does NOT count: casual mention anywhere in commit body, or t-NNN appearing only in a chore/docs/sync commit.
Pure functions (testable)
-
extract_task_ids_from_git_log(log: &str) -> Vec<String>Parse rawgit log --all --onelineoutput. Return unique task IDs matching the precision patterns above. -
find_shipped_pending<'a>(pending: &'a [&serde_json::Value], shipped_ids: &[String]) -> Vec<&'a serde_json::Value>Cross-reference: return pending tasks whose ID appears inshipped_ids.
Flags
--dry-run— print what would be closed, no writes--batch N— batch size (default 10)--yes— close all without prompting (for automation)--git-dir <path>— override repo path (default: CWD)
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.
- 10d ago First seen · 40 lines · 0 tokens per session scan A 41839652dc3f
triage_stale.spec is a command published in the GitHub repository martineserios/thebrana (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 447 tokens. 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-08-31.
Other commands, from other repositories
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
start-issue
You are beginning work on GitHub issue $ARGUMENTS.
hybrid-complete
Complete Hybrid Ralph task in worktree, verify all stories complete, commit code changes (excluding planning files), merge to target branch, and cleanup worktree directory. Can be run from any directory.
log
A command definition for recording completed work as a phase log, including the user request, actions, results, decisions and next steps.
status
A command that shows a project’s progress by phase. It must use a separate status skill, which reads the project index and configuration before displaying the summary.
sync-github
Ejecuta SonIA Sync: refleja el tablero local en GitHub Issues usando gh CLI.