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/narpatsinghpurohit/tstack/claude-mdgit clone --depth 1 https://github.com/narpatsinghpurohit/tstackWrote 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/narpatsinghpurohit/tstack/claude-md)<a href="https://agentmods.dev/instructions/narpatsinghpurohit/tstack/claude-md"><img src="https://agentmods.dev/badge/instructions/narpatsinghpurohit/tstack/claude-md.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.01609 | $0.01609 |
| Opus 5 | $0.00805 | $0.00805 |
| Sonnet 5 | $0.00322 | $0.00322 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
tstack CLAUDE.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 4d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Config
| Setting | Value |
|---|---|
| Project name | tstack |
| Shared package | @tstack/shared |
| Backend | apps/api/ (NestJS, port 8000) |
| Web | apps/web/ (React + Vite, port 5173) |
| Mobile | apps/mobile/ (React Native) |
| Database | MongoDB + Mongoose |
| Auth | JWT (access + refresh tokens) |
| Multi-tenant field | orgId |
| Tenant entity | Organization |
| Package manager | bun |
| Linter | Biome |
| Queue | BullMQ + Redis |
| Nodemailer (SMTP) |
Skills and agents read this table to adapt to your project. Update values above when forking for a new project. For example, change
orgIdtoworkspaceIdorcompanyIdif that fits your domain.
Project overview
Multi-tenant SaaS starter kit (Turborepo + Bun monorepo). NestJS + Mongoose backend, React 19 + Vite web frontend, React Native mobile app. Zod schemas shared between all apps via the shared package. Fork this repo and build your product on top.
Quick reference
| What | Where |
|---|---|
| Backend | apps/api/ |
| Web frontend | apps/web/ |
| Mobile app | apps/mobile/ |
| Shared schemas | packages/shared/src/schemas/ |
| Permission constants | packages/shared/src/constants/ |
| Permission helpers | packages/shared/src/permissions/ |
| Types | packages/shared/src/types/ |
| Feature specs | specs/ |
Commands
bun install # Install all deps
bun run dev # Start all apps (Turborepo)
bun run build # Build all
bun run lint # Biome check
bun run test # Run all tests
bun run type-check # TypeScript check
bun seed # Run all seeders
bun seed --fresh # Re-seed (overwrites role permissions)
bun seed --class=X # Run single seeder
Architecture rules
Backend (NestJS)
- Controller → Service → Repository → Mongoose (never skip layers)
- Every entity repository extends
BaseRepository(auto-scopes queries by tenant field) - Every endpoint needs
@Can(PERMISSIONS.X)or@CanAny(...)+@CurrentUser()for tenant scoping - Validation via
ZodValidationPipewith schemas from the shared package - DTOs defined ONLY in
packages/shared/src/schemas/, never locally - Seeding via
DatabaseSeederwith dedicatedSeederclasses - Queue processing via BullMQ processors in
core/queue/
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.
- 4d ago First seen · 142 lines · 1,609 tokens per session scan A 5dd15c9431df
tstack CLAUDE.md is an instructions file published in the GitHub repository narpatsinghpurohit/tstack (5 stars, last pushed 5mo ago), licensed MIT. It adds 1,609 tokens to every session, about $0.0080 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-31.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.