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/dchu917/ctx/ctx-branchgit clone --depth 1 https://github.com/dchu917/ctxWrote 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/dchu917/ctx/ctx-branch)<a href="https://agentmods.dev/commands/dchu917/ctx/ctx-branch"><img src="https://agentmods.dev/badge/commands/dchu917/ctx/ctx-branch.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.00097 |
| Opus 5 | $0.00000 | $0.00048 |
| Sonnet 5 | $0.00000 | $0.00019 |
| Haiku 4.5 | $0.00000 | $0.00010 |
Grade A, and why
ctx-branch 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 3d 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
Experimental integration for branching ctx workstreams in Cursor.
Treat any extra text after /ctx-branch as the argument string for ctx branch.
Run:
ctx branch <arguments>
If ctx is unavailable, fall back to:
python3 scripts/ctx_cmd.py branch <arguments> --format markdown
After the command returns, summarize the new branch briefly, mention the inherited context, and ask how the user wants to proceed.
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.
- 3d ago First seen · 18 lines · 0 tokens per session scan A 97df5da5ab24
ctx-branch is a command published in the GitHub repository dchu917/ctx (128 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 97 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
debug
Systematic debugging with hypotheses and evidence gathering.
whats-next
Show current project status and suggest next steps.
recover
Scan orphaned worktrees and stale branches, then offer explicit approval-gated cleanup.
capture
Triage raw inbox notes into reviewed repository destinations without deleting their sources.
resume
恢复本 session 的 PACEflow（删除 pause 标志）.
migrate-gemini
Inventory and migrate selected Gemini CLI workflows with dry-run review and parity checks.