Borrowing it
Nothing to install: this file belongs to bronz3beard/ai.tech-lead-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/bronz3beard/ai.tech-lead-stack/main/AGENTS.mdgit clone --depth 1 https://github.com/bronz3beard/ai.tech-lead-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/bronz3beard/ai.tech-lead-stack/agents-md)<a href="https://agentmods.dev/instructions/bronz3beard/ai.tech-lead-stack/agents-md"><img src="https://agentmods.dev/badge/instructions/bronz3beard/ai.tech-lead-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/bronz3beard/ai.tech-lead-stack/agents-md"><img src="https://agentmods.dev/badge/instructions/bronz3beard/ai.tech-lead-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.01823 | $0.01823 |
| Opus 5.5 | $0.00729 | $0.00729 |
| Sonnet 5.5 | $0.00365 | $0.00365 |
| Haiku 4.5 | $0.00182 | $0.00182 |
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 16d 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 — 125 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.
packages/core/src/install/{surfaces,reconcile,refresh,lock,version}.mjs run
inside the MCP server at every start (they refresh users' installed editor
files): async I/O only (a test fails on any *Sync( call), stderr only, and
TS files that core Jest loads must not import them (Jest cannot require .mjs).
MCP tool naming & skill acquisition contract
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.
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.
- 16d ago Changed · +5 lines · +80 tokens per session 5458a0e18712
- 23d ago Changed · +31 lines · +517 tokens per session df4908670470
- 1mo ago Changed · +20 lines · +429 tokens per session 0017ff9f1e83
- 1mo 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 3d ago), licensed MIT. It adds 1,823 tokens to every session, about $0.0073 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-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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.