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/techtankto/techtank-site/agents-mdgit clone --depth 1 https://github.com/techtankto/techtank-siteWrote 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/techtankto/techtank-site/agents-md)<a href="https://agentmods.dev/instructions/techtankto/techtank-site/agents-md"><img src="https://agentmods.dev/badge/instructions/techtankto/techtank-site/agents-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.01786 | $0.01786 |
| Opus 5 | $0.00893 | $0.00893 |
| Sonnet 5 | $0.00357 | $0.00357 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade A, and why
techtank-site 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 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for any coding agent working in this repository. This is the
primary, tool-agnostic context source for AI agents (Claude Code, Cursor,
Copilot, Codex, etc.); tool-specific files like CLAUDE.md defer to it.
What this repo is
A Next.js (App Router) implementation of techtankto.com, Toronto's volunteer-run tech community website. The redesign moves away from a flat "link-tree" layout toward a conversion-oriented onboarding hub that funnels visitors into specific roles — attendee, speaker, host, sponsor, or volunteer.
The PRD (docs/prd/) is kept as a historic record of how the current
structure came to be — read it for context on prior decisions (why a route
was shaped the way it was, what a design token replaced), not as a spec to
keep in sync going forward. House standards (process, writing, nextjs, components, data,
testing, performance, accessibility, seo, git) are supplied by the vendored
skills under .claude/skills/ / .agents/skills/ and load automatically via
skill discovery. Application code lives in app/, with shared pieces in
components/, constants/, and public/. The initial UI scaffold was
generated from the prior PRD via v0 —
original prompt and generation.
For developer-facing setup (scripts, directory tree, route map), see
README.md.
Repository layout
.
├── AGENTS.md # This file — primary agent context
├── CLAUDE.md # Claude Code stub that includes AGENTS.md
├── .agents/skills/ # vendored house-standard skills (copied, portable)
├── .claude/skills/ # same skills (symlinked to .agents/skills/)
└── docs/
└── prd/ # 01-brief → 06-plan, the numbered pipeline
docs/prd/06-plan.md records the milestone list as it stood during the
redesign. docs/prd/03-solution.md documents the route map and per-surface
content requirements as originally specified — read it to understand why a
surface is shaped the way it is, not as the current route reference (see
README.md for that).
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 · 153 lines · 1,786 tokens per session scan A 53992fef5fa9
techtank-site AGENTS.md is an instructions file published in the GitHub repository techtankto/techtank-site (5 stars, last pushed 2d ago), licensed MIT. It adds 1,786 tokens to every session, about $0.0089 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.