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/cesarferreira/stax/sweepgit clone --depth 1 https://github.com/cesarferreira/staxWrote 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/cesarferreira/stax/sweep)<a href="https://agentmods.dev/commands/cesarferreira/stax/sweep"><img src="https://agentmods.dev/badge/commands/cesarferreira/stax/sweep.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.00000 | $0.00909 |
| Opus 5 | $0.00000 | $0.00454 |
| Sonnet 5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
sweep 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
stax sweep
Classify all local branches and optionally delete the safe-to-remove ones.
Why sweep?
Over time a repo accumulates branches that were merged, whose PR was closed, or that were abandoned as work-in-progress. stax sync already cleans up stax-tracked merged branches during rs, but it ignores untracked branches and has no read-only listing mode.
stax sweep fills both gaps:
- Operates on every local branch (tracked and untracked).
- Lists branches grouped by status so you can see what's accumulating.
- Deletes only what you explicitly ask for, never touching trunk or the current branch.
Branch statuses
| Status | Meaning |
|---|---|
merged |
Ancestor of trunk, PR metadata says merged, or a stax-tracked PR branch has a deleted upstream |
upstream-gone |
Remote tracking ref is [gone] and the branch has no commits unique to local or remote trunk |
stale |
Last commit older than the configured threshold (default 30 days) |
active |
Everything else |
Precedence when a branch matches multiple: merged > safe upstream-gone > stale > active. Ordinary upstream-gone branches with unique commits are treated as active so cleanup cannot delete local-only work.
Usage
# Read-only: classify all local branches and print a grouped summary
stax sweep
# Delete merged branches and upstream-gone branches with no unique work, with confirmation
# Stax-tracked PR branches are also merged when PR metadata says merged or the upstream was deleted
stax sweep --delete
# Also include stale branches in the deletion set
stax sweep --delete --include-stale
# Skip the confirmation prompt
stax sweep --delete --force
# Override the stale threshold
stax sweep --stale-days 60
# Machine-readable output (conflicts with --delete)
stax sweep --json
Flags
| Flag | Description |
|---|---|
--delete |
Delete merged branches, tracked merged PR branches, and upstream-gone branches with no unique work after confirmation |
--include-stale |
Extend deletion to stale branches (requires --delete) |
--force |
Skip confirmation prompt (requires --delete) |
--stale-days <N> |
Override stale threshold in days (default: 30) |
--json |
Output classification as JSON; conflicts with --delete |
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.
- 6d ago First seen · 100 lines · 0 tokens per session scan A 919a8f87a052
sweep is a command published in the GitHub repository cesarferreira/stax (124 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 909 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.