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/amanvarshney01/create-better-t-stack/newgit clone --depth 1 https://github.com/AmanVarshney01/create-better-t-stackWhat 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.00033 | $0.00367 |
| Opus 5 | $0.00016 | $0.00183 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
new 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
Create a Better-T-Stack project
User request: $ARGUMENTS
Scaffold a new project using the Better-T-Stack MCP server. Do not hand-roll the project structure, tooling, auth, or database wiring.
Steps
- Parse the request. Extract the project name and any stack preferences from the arguments above. If nothing was provided, ask what kind of project they want.
- Resolve unknowns. For any major choice not specified, either ask a brief question or pick a sensible default and state it. Call
bts_get_stack_guidanceandbts_get_schemawhen you need the authoritative option list or rules. - Build a full explicit config. Every field must be set explicitly (use
"none",[],true/false). Required:projectName,frontend,backend,runtime,database,orm,api,auth,payments,addons,examples,git,packageManager,install,dbSetup,webDeploy,serverDeploy. - Plan with
bts_plan_project(dry run). Show the resolved stack and confirm it matches intent. - Create with
bts_create_projectonce confirmed. Useinstall: falseto avoid MCP timeouts. - Report the stack and the exact next commands (
<packageManager> install,dev, any DB setup).
Always plan before create. Never send a partial config.
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 · 22 lines · 33 tokens per session scan A 5cb78acb6506
new is a command published in the GitHub repository AmanVarshney01/create-better-t-stack (5,691 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 367 once invoked, about $0.0002 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
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
code-review-swarm
Deploy specialized AI agents to perform comprehensive, intelligent code reviews that go beyond traditional static analysis.
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.