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 agentmods add commands/kayba-ai/agentic-context-engine/list-branchesgit clone --depth 1 https://github.com/kayba-ai/agentic-context-engineWrote 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/kayba-ai/agentic-context-engine/list-branches)<a href="https://agentmods.dev/commands/kayba-ai/agentic-context-engine/list-branches"><img src="https://agentmods.dev/badge/commands/kayba-ai/agentic-context-engine/list-branches.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 | $0.00000 | $0.00390 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
list-branches 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 4d 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
List project branches with their worktree status.
Arguments: $ARGUMENTS (optional filters)
- No args: List all branches matching naming convention
<type>/<developer>/<description> --all: Include all branches (not just convention-named)--worktrees: Only show branches with active worktrees<type>: Filter by type (feature, fix, docs, refactor, test, chore)
Examples:
/list-branches→ all convention-named branches/list-branches feature→ only feature branches/list-branches --worktrees→ only branches with worktrees/list-branches --all→ all branches including main
Steps:
- Get all local branches:
git branch --format='%(refname:short)' - Get worktree list:
git worktree list --porcelain - Parse worktree output to map branches to paths
- Filter branches based on arguments
- Format and display results
Output format:
Branch Worktree Status
──────────────────────────────────────────────────────────────────────────────
* main . current
feature/john/add-caching ../feature-john-add-caching active
fix/jane/login-error (no worktree) -
Summary: 3 branches, 2 with worktrees
Column meanings:
*indicates current branch- Worktree shows path relative to repo root, or "(no worktree)" if none
- Status: "current" (HEAD), "active" (has worktree), "-" (no worktree)
Tips shown after output:
- To create a worktree for a branch:
git worktree add ../<path> <branch> - To remove a branch with worktree: use
/remove-branch <branch>
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.
- 4d ago First seen · 41 lines · 0 tokens per session scan A 8c0672da1633
list-branches is a command published in the GitHub repository kayba-ai/agentic-context-engine (2,564 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 390 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-30.
Other commands, from other repositories
dream-apply
Walk a dream proposal artifact, review each item, apply accepted ones, commit.
end
End a session — log what happened and propose durable memory updates.
dream
Run a curator pass over the memory dir. Produces a proposal artifact for /dream-apply. Default curator: rot.
start
Start a session — load context + memory and brief yourself on current state.
update
Mid-session checkpoint — save progress without ending the session.
begin
Begin a coding session — scan code, show overview, turn on smart mode.