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/barnett-studios/cxpak/tracegit clone --depth 1 https://github.com/Barnett-Studios/cxpakWhat 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.00017 | $0.00301 |
| Opus 5 | $0.00009 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
trace 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 2d 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
/cxpak:trace
Trace a symbol through the codebase dependency graph.
Steps
-
Parse arguments. The user must provide a symbol name (e.g.,
/cxpak:trace handle_request). If no symbol is provided, ask for one. The user may also provide a path (default.) and--allfor full BFS traversal. -
Ask for token budget. Ask: "Token budget for the trace? (default: 50k)" Use their answer or default to
50k. -
Resolve cxpak binary:
CXPAK="$("${CLAUDE_PLUGIN_ROOT}/lib/ensure-cxpak")" -
Run the trace:
"$CXPAK" trace --tokens <budget> --format markdown [--all] <symbol> <path>Add
--allonly if the user requested full graph traversal. -
Present the output. The trace contains:
- The target symbol and where it's defined
- Files that use/call the symbol (dependencies)
- Full source of relevant files, prioritized by dependency distance
-
Explain what was found. Summarize the symbol's role and how it connects to the rest of the codebase.
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.
- 2d ago First seen · 32 lines · 17 tokens per session scan A 696aea6a6c7e
trace is a command published in the GitHub repository Barnett-Studios/cxpak (25 stars, last pushed 4d ago), licensed Apache-2.0. It adds 17 tokens to every session and 301 once invoked, about $0.0001 per session on Opus 5. 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.