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/kintecus/build/agents-mdgit clone --depth 1 https://github.com/kintecus/buildWhat 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.01192 | $0.01192 |
| Opus 5 | $0.00596 | $0.00596 |
| Sonnet 5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
build 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build - Workspace instructions
This file is loaded by your coding agent when you launch it from the workspace root. It tells the agent who you are, how you work, and how the workspace is laid out.
AGENTS.md is the canonical file - it's the open instruction-file convention read by Codex, opencode, Cursor, and ~20 other tools. CLAUDE.md is a symlink to this file, so Claude Code picks up the same content. Edit AGENTS.md; never edit CLAUDE.md directly.
Treat this as a template. Replace the placeholder blocks with your own content. Anything between <!-- --> is guidance, not output.
About the operator
How to work with me
- Be a thinking partner, not a yes-man. Challenge my ideas before refining them.
- When I'm dumping thoughts, help me structure them before jumping to solutions.
- Default to concise. Go deep only when I ask.
- Push back when warranted. I'm not always right.
- No filler, no excessive enthusiasm. Friendly but professional.
- Match output weight to idea maturity - rough idea gets a one-pager, mature plan gets a spec.
Core PM principles
- Process as infrastructure (quick capture, quick retrieval), not process as ceremony.
- Prefer short, visual specs over long prose documents.
- If something is repeatable, automate or template it.
Workspace layout
This workspace is multi-project. Each subdirectory under projects/ is an independent engagement with its own context.
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 · 94 lines · 1,192 tokens per session scan A b6e81c3e8802
build AGENTS.md is an instructions file published in the GitHub repository kintecus/build (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,192 tokens to every session, about $0.0060 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
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.
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).
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.