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/tonyghiani/ai-essentials/agents-mdgit clone --depth 1 https://github.com/tonyghiani/ai-essentialsWrote 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/tonyghiani/ai-essentials/agents-md)<a href="https://agentmods.dev/instructions/tonyghiani/ai-essentials/agents-md"><img src="https://agentmods.dev/badge/instructions/tonyghiani/ai-essentials/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.01354 | $0.01354 |
| Opus 5 | $0.00677 | $0.00677 |
| Sonnet 5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00135 | $0.00135 |
Grade A, and why
ai-essentials 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-essentials
Agent configuration for this repository. Install globally via symlinks (see README.md) or reference these paths when working inside this repo.
Always apply
For Claude Code these two, plus verification discipline and a compact TS/React invariants block, are assembled in claude/CLAUDE.md.
Code style (file-scoped)
Each rule activates on its own globs. Read the one matching the file you are editing.
| Editing | Rule |
|---|---|
any .ts / .tsx |
rules/typescript-style.mdc |
| adding files, folders, or imports | rules/project-structure.mdc |
| components and hooks | rules/react-components.mdc |
| server, services, routes | rules/node-api-patterns.mdc |
*.test.ts(x) / *.spec.ts(x) |
rules/testing-style.mdc |
These encode Marco's conventions, confirmed by a 69-question style interview against 40 merged PRs and five personal repositories. Project conventions win where they conflict; read the neighbouring files first.
Mechanical rules (formatting, import order, enums, any, naming casing) are config, not guidance.
They live in eslint-recommendations.md and stay out of the rule files
on purpose.
React (frontend files only)
Effect, dependency, and ref discipline is separate from component structure:
These rules target *.{tsx,jsx} and paths under components/, hooks/, pages/, and app/. Skip them for backend-only or config-only changes.
Claude Code loads the same material on demand via the react-patterns skill.
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 · 98 lines · 1,354 tokens per session scan A cabddd321eea
ai-essentials AGENTS.md is an instructions file published in the GitHub repository tonyghiani/ai-essentials (6 stars, last pushed 26d ago), licensed MIT. It adds 1,354 tokens to every session, about $0.0068 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.