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 instructions/amanvarshney01/create-better-t-stack/agents-mdgit 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.00938 | $0.00938 |
| Opus 5 | $0.00469 | $0.00469 |
| Sonnet 5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
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 3d 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 — 81 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 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.
- 3d 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,691 stars, last pushed 2d ago), licensed MIT. It adds 938 tokens to every session, about $0.0047 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 instructions, from other repositories
vobase CLAUDE.md
Instructions for vobase/vobase, covering vobase monorepo, packages, commands, quality rules and architecture.
flarestarter AGENTS.md
Instructions for FlareStarter/flarestarter, covering agents.md, what this is, structure, conventions and commands.
flarestarter CLAUDE.md
Instructions for FlareStarter/flarestarter: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
svelteflare AGENTS.md
Instructions for pinebasedev/svelteflare, covering agent rules for this project, theme fidelity (non-negotiable), talking to the user and deep-dive skills.
openmonetis AGENTS.md
AGENTS.md instructions for felipegcoutinho/openmonetis, covering agents.md - openmonetis, related projects, critical rules, architecture and feature-first.
builders-stack AGENTS.md
Instructions for lonormaly/builders-stack, covering agents.md — the primer for coding agents, rule zero — worktrees are temporary and share dependencies, 1. the mental model — the buckets, 2. the map — all 17 packages and 3. the laws — do not break these.