Better-T-Stack is a command-line tool that generates end-to-end, type-safe TypeScript project scaffolds from selectable frontend, backend, database, authentication, and tooling options. Developers use it to start full-stack applications with a stack tailored to their needs. The catalogue includes skills, agents, commands, an MCP server, and a plugin for having coding agents plan and generate Better-T-Stack projects.
Borrowing it
Nothing to install: this file belongs to AmanVarshney01/create-better-t-stack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AmanVarshney01/create-better-t-stack/main/AGENTS.mdgit clone --depth 1 https://github.com/AmanVarshney01/create-better-t-stackWrote 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/instructions/amanvarshney01/create-better-t-stack/agents-md)<a href="https://agentmods.dev/instructions/amanvarshney01/create-better-t-stack/agents-md"><img src="https://agentmods.dev/badge/instructions/amanvarshney01/create-better-t-stack/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/amanvarshney01/create-better-t-stack/agents-md"><img src="https://agentmods.dev/badge/instructions/amanvarshney01/create-better-t-stack/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00933 | $0.00933 |
| Opus 5.5 | $0.00373 | $0.00373 |
| Sonnet 5.5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
create-better-t-stack AGENTS.md 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repo is a Bun + Turborepo monorepo.
apps/cli: published CLI (create-better-t-stack), with source inapps/cli/srcand tests inapps/cli/test.apps/web: Next.js docs/site (apps/web/src,apps/web/content/docs,apps/web/public).packages/template-generator: template generation engine used by the CLI.packages/types: shared schemas/types.packages/backend: Convex backend used by web features.plugin/: installable agent plugin (Claude Code + Codex) — skills, commands, and MCP wiring; published via the root marketplaces (.claude-plugin/,.agents/plugins/).
Build, Test, and Development Commands
bun install: install workspace dependencies.bun dev:cli: watch-build CLI package.bun dev:web: run web app locally (next dev --port 3333).bun build: build all packages/apps through Turbo.bun build:cli: build only the CLI target.bun run check: format + lint (oxfmt . && oxlint .).cd apps/cli && bun run test: run CLI integration tests.
Coding Style & Naming Conventions
- Language: TypeScript (strict mode enabled across projects).
- Modules: ESM-first (
"type": "module"where applicable). - Formatting/linting:
oxfmtandoxlint; runbun run checkbefore committing. - File naming: prefer kebab-case files (for example
database-setup.ts). - Symbols:
camelCasefor functions/variables,PascalCasefor types/components. - Keep feature logic near domain folders (
helpers,utils,template-handlers).
Error Handling Conventions
- In CLI code, prefer
better-resultover ad-hoctry/catchfor recoverable flows. - Return typed
Result<T, E>and useResult.ok,Result.err,Result.try, andResult.tryPromise. - Reuse domain errors from
apps/cli/src/utils/errors.ts(CLIError,ProjectCreationError,UserCancelledError) and convert thrown prompt errors at boundaries.
Template Authoring (Handlebars)
- Templates live in
packages/template-generator/templatesand use helpers frompackages/template-generator/src/core/template-processor.ts(eq,ne,and,or,includes). - For conditional ORM-specific output, use helper form with quoted values:
{{#if (eq orm "prisma")}}{{else if (eq orm "drizzle")}}{{/if}}- Example:
packages/template-generator/templates/packages/infra/alchemy.run.ts.hbs.
- When files must contain literal
{{ ... }}(Vue/JSX/template syntax), escape opening braces as\{{in.hbsfiles so Handlebars does not evaluate them.- Example:
packages/template-generator/templates/frontend/nuxt/app/pages/index.vue.hbs.
- Example:
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 · -3 tokens per session bd2dcbfd9091
- 1mo ago Changed · +1 lines · +43 tokens per session 47c7f70debb8
- 1mo ago Changed · -4 lines · -45 tokens per session 501a0b0005be
- 1mo ago First seen · 81 lines · 938 tokens per session scan A e828b642dab6
create-better-t-stack AGENTS.md is an instructions file published in the GitHub repository AmanVarshney01/create-better-t-stack (5,824 stars, last pushed yesterday), licensed MIT. It adds 933 tokens to every session, about $0.0037 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).