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/bronz3beard/ai.tech-lead-stack/agents-mdgit clone --depth 1 https://github.com/bronz3beard/ai.tech-lead-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.00797 | $0.00797 |
| Opus 5 | $0.00398 | $0.00398 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
ai.tech-lead-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 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Read automatically by Jules — and by Cursor, Copilot, and most other AGENTS.md-aware tools — at the start of every task. This is the persistent version of the "Standing Rules" block in
docs/designs/2026-07-08-jules- prompts.md. Once this file is committed to the repo root, you no longer need to paste that block before each prompt.This file is the cross-tool entry point.
.ai/agents.mdremains the internal, MCP/skill-oriented convention for IDE agents working in a local checkout (Antigravity, Cursor, VS Code) — the two complement each other and should not drift apart. Deeper per-workstream detail lives indocs/designs/and in each PROMPT's own text; this file stays short on purpose.
Commands
npm run check-types && npm test && npm run validate:skills # run + paste output before opening any PR
npm run format:check && npm run lint # must also pass
Stack quirks
This project pins a Next.js version with breaking changes from what most
training data expects — APIs, conventions, and file structure may differ. Read
the relevant guide in node_modules/next/dist/docs/ before writing any Next.js
code. Heed deprecation notices. This is Pillar 1 in practice: ground decisions
in what's actually installed, not what's familiar.
MCP tool naming
If your client connects to the tech-lead-stack MCP server (e.g. Cursor,
Antigravity, or a web chat UI) and a tool call like get_skills or
verify_mission_alignment fails as "not found," the client may have prefixed
the tool name — check for mcp_tech-lead-stack_<tool> or
tech-lead-stack_<tool> in your available tools list and call the resolved
name. Not applicable if your environment doesn't connect to this MCP server.
Four Pillars — non-negotiable, and how your output is graded
- G-Stack / Diagnosis-First — Phase 0 before any code: read
package.json,tsconfig.json,prisma/schema.prisma, and the files named in your task. Ground every decision in what actually exists here. - MinimumCD / Atomic Batches — vertical slices under 100 LOC per commit, each independently verifiable. Never one big-bang commit.
- Production-Grade Ethos — no "tests later," no "seems right." Every slice ends with real command output pasted into the PR. Catching yourself rationalizing a shortcut is the signal to stop and do it properly instead.
- Modern Web Guidance — UI/web-facing code uses Server Components, Zod validation, semantic HTML/ARIA. No legacy workarounds.
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 · 69 lines · 797 tokens per session scan A f1c5bb1b952f
ai.tech-lead-stack AGENTS.md is an instructions file published in the GitHub repository bronz3beard/ai.tech-lead-stack (3 stars, last pushed 2d ago), licensed MIT. It adds 797 tokens to every session, about $0.0040 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
thinkrail AGENTS.md
Instructions for JetBrains/thinkrail, covering thinkrail, module structure & boundaries (top-priority requirement), engine: pi only, in-process, architecture (three rings) and repo layout.
raytsystem-public-os CLAUDE.md
Instructions for romarayt/raytsystem-public-os, covering compatibility pointer and documentation synchronization.
raytsystem-public-os AGENTS.md
Instructions for romarayt/raytsystem-public-os, covering raytsystem — agent routing, invariants, commands, skill routing and documentation.
examples CLAUDE.md
Claude Code instructions for rossoctl/examples, covering claude.md - agent examples, repository structure, key commands, code style and dco sign-off (mandatory).
pilot CLAUDE.md
Claude Code instructions for qf-studio/pilot, covering pilot: ai that ships your tickets, who is reading this file?, ⚠️ git & worktree discipline (all sessions), quick commands and plan a feature (navigator).
metatron CLAUDE.md
Instructions for kerbelp/metatron, covering claude.md, what metatron is, tech stack (decided — not open for debate), core principle and source of truth (depends on deployment).