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/coregit 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/core)<a href="https://agentmods.dev/commands/cesarferreira/stax/core"><img src="https://agentmods.dev/badge/commands/cesarferreira/stax/core.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.02392 |
| Opus 5 | $0.00000 | $0.01196 |
| Sonnet 5 | $0.00000 | $0.00478 |
| Haiku 4.5 | $0.00000 | $0.00239 |
Grade A, and why
core 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 today.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core commands
Day-to-day commands you'll use most. For the exhaustive list of every command, subcommand, and flag, see the full reference.
Stack view and creation
| Command | What it does |
|---|---|
st |
Launch the interactive TUI |
st web [path] |
Open a localhost HTMX web workspace in the browser (127.0.0.1 only) |
st ls |
Show stack with PR, rebase, and metadata-repair status |
st ll |
Like st ls plus PR URLs and detail |
st create <name> / st add <name> |
Create a branch stacked on current |
st create --ai -a --yes |
Generate branch name + first commit message |
st create <name> --below |
Insert a new branch below current, carrying tracked/untracked prepared changes with it |
| `st get [branch | PR]` |
If you discover a hotfix while working upstack, keep the edits in place:
st create cve-hotfix --below
st create --below -am "fix: patch CVE-2026-0001"
--below auto-stashes prepared tracked and untracked changes before moving to the lower base, then reapplies them on the inserted branch. With -am, those changes are staged and committed on the new lower branch.
When -m or --ai derives a branch name that already exists, Stax stops instead of creating a suffixed duplicate; pass an explicit different name or checkout/reparent the existing branch.
Submit and merge
| Command | What it does |
|---|---|
st ss |
Submit the whole stack — open or update linked PRs |
st stack link |
Register the current PR stack as a native GitHub Stack when gh-stack is available |
st stack unlink [<stack-number>] |
Unstack a remote native Stack by number, or the active locally tracked stack when omitted |
st branch submit |
Submit only the current branch; if its parent is already synced to the remote, Stax may publish a temporary rebased head without moving your local branch |
st upstack submit |
Submit current branch and descendants; descendants are temporarily chained onto any temporary parent publish heads |
st draft [branch] |
Convert the current (or named) branch's PR to draft |
st draft --stack |
Convert every PR in the current stack to draft |
st undraft [branch] |
Mark the current (or named) branch's PR as ready for review |
st undraft --stack |
Mark every PR in the current stack as ready for review |
st ready |
Interactive PR readiness dashboard — CI, review approval, and merge state for unmerged tracked PRs; auto-refreshes every 15s, drops remotely merged PRs, and stays open until you quit (q) |
st merge |
Cascade-merge from stack bottom up to current branch |
st merge --when-ready |
Wait for CI + approvals, then merge (alias: st mwr) |
st merge --downstack-only / --ds |
Merge ancestors below current, then rebase current branch |
st merge --stack |
Target selected PRs/MRs to trunk and merge the tip with SHA-preserving merge, allowing GitHub or GitLab to mark lower items merged (--full includes descendants); delegates to gh stack merge for atomic landing when the repo has a confirmed-enabled native GitHub Stack and gh-stack v0.1.0+ |
st merge --remote |
Merge remotely via the GitHub API while you keep working |
st merge --all |
Merge the entire stack regardless of where you are |
st cascade |
Restack, push, and create/update PRs in one shot (no trunk fetch; offline-friendly) |
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.
- today Changed 5381f7b28f82
- 4d ago First seen · 111 lines · 0 tokens per session scan A 4cffaf55a9b7
core is a command published in the GitHub repository cesarferreira/stax (124 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,392 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
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.