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/shahsagarm/sagarshah.dev/agents-mdgit clone --depth 1 https://github.com/shahsagarm/sagarshah.devWhat 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.02226 | $0.02226 |
| Opus 5 | $0.01113 | $0.01113 |
| Sonnet 5 | $0.00445 | $0.00445 |
| Haiku 4.5 | $0.00223 | $0.00223 |
Grade A, and why
sagarshah.dev 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 3d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is NOT the Next.js you know
This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
sagarshah.dev v2
Single-page portfolio (live at sagarshah.dev). Next.js 16.2.12 (App Router, Turbopack default) · React 19 · TypeScript 5.9 strict · Tailwind CSS v4 (CSS-first — there is no tailwind.config.*; the theme lives in src/app/globals.css via @theme). Package manager: npm. Node >= 22.18 required — scripts/check-*.mjs import .ts files relying on Node's built-in type stripping.
Deliberately minimal dependencies: no UI/animation/state libraries. Runtime deps beyond the framework are only lucide-react, clsx, tailwind-merge, @next/third-parties, @vercel/analytics + @vercel/speed-insights. Keep it that way.
Commands
npm run dev— dev server (never add--turbopack; it is the Next 16 default)npm run verify— the gate:tsc --noEmit && eslint . && check-tokens && check-anchors && check-duration && next build. Run before declaring any task done.npm run typecheck/npm run lint— individual steps (next lintno longer exists in Next 16; lint is bare eslint)npm run check:duration—node:assertchecks forsrc/lib/duration.ts; the closest thing to unit tests. There is no test framework. It also asserts total career length stays in [120, 144) months — around late 2027 this starts failingverifyby design (staleness alarm: revisit the "decade" copy and the bounds; do not patchduration.tsto silence it).npm run icons:generate— rebuilds thepublic/PWA icons from a 1024px master (Next's vendored@vercel/og+sharp). Not part ofverify. Its hardcodedrgb()literals are deliberate — Satori resolves no CSS variables andcheck-tokensscans onlysrc/— do not "fix" them into tokens.- Lighthouse:
npm run build && npm start, thennpm run lh:mobile/npm run lh:desktop(reports land in.next/lighthouse/, wiped by each build). Never audit the dev server — if/tokensreturns 200 you are on dev and every number is wrong. - Prettier (+
prettier-plugin-tailwindcss) is editor-only: no format script, not inverify.
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.
- 3d ago First seen · 49 lines · 2,226 tokens per session scan A 335bfeed2df3
sagarshah.dev AGENTS.md is an instructions file published in the GitHub repository shahsagarm/sagarshah.dev (108 stars, last pushed 29d ago), licensed MIT. It adds 2,226 tokens to every session, about $0.0111 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-30.
Other instructions, from other repositories
al-folio AGENTS.md
AGENTS.md instructions for alshedivat/al-folio, covering agent guidelines for al-folio (v1.x), route your change, stop sign, three failures that produce no error message and validated local command set.
al-folio CLAUDE.md
Claude Code instructions for alshedivat/al-folio, covering claude.md, daily dev loop, optional toolchains, docker serving model (v1-specific) and ci gates and the style contract.
al-folio copilot-instructions.md
Copilot instructions for alshedivat/al-folio, covering copilot coding agent instructions (v1.x), where to look, copilot-specific paths and ci expectations.
al-folio javascript-scripts.instructions.md
Instructions for alshedivat/al-folio, covering javascript instructions (v1.x), ownership, guidance and validation.
al-folio liquid-templates.instructions.md
Instructions for alshedivat/al-folio, covering liquid templates instructions (v1.x), ownership, guidance and validation.
al-folio markdown-content.instructions.md
Instructions for alshedivat/al-folio, covering markdown content instructions (v1.x), guidance and validation.