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/letitbk/claude-academic-setup/agents-mdgit clone --depth 1 https://github.com/letitbk/claude-academic-setupWrote 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/letitbk/claude-academic-setup/agents-md)<a href="https://agentmods.dev/instructions/letitbk/claude-academic-setup/agents-md"><img src="https://agentmods.dev/badge/instructions/letitbk/claude-academic-setup/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.00426 | $0.00426 |
| Opus 5 | $0.00213 | $0.00213 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
claude-academic-setup 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 5d 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.
What it actually says
AGENTS.md
Agent-agnostic guidelines for Codex, Gemini/Antigravity, Cursor, and other agents. Mirrors
CLAUDE.md— keep the two in sync so every agent honors the same rules.
Precedence: system constraints > explicit user request > project AGENTS.md/CLAUDE.md > this file. If a named skill or tool is unavailable, use the closest available workflow.
1. Use Skills When Relevant
When starting a new task, check for clearly relevant skills and invoke them first. Key triggers:
- Session start →
napkin - New data →
datacheck - Plots →
viz - Prose →
humanizer/stop-slop - Creative work →
brainstorming
Use AskUserQuestion (via ToolSearch) for structured questions. Fall back to plain text if unavailable.
2. Think Before Coding
- State assumptions. If uncertain, ask.
- Multiple interpretations → present them, don't pick silently.
- Simpler approach exists → say so.
3. Simplicity First
- No features, abstractions, or error handling beyond what's needed.
- Prefer concise solutions. If it looks overcomplicated, simplify.
4. Surgical Changes
- Don't improve, refactor, or reformat code you weren't asked to change.
- Match existing style. Assume the worktree may be dirty.
- Remove only orphans YOUR changes created.
- Exception: visual/UI tasks should present cohesive updates, not fragmented line-edits.
5. Reproducible Evidence
When running substantive analysis (not one-liners or sanity checks):
- Capture output via
teetologs/YYYY-MM-DD_HH-MM-SS_<description>.log - Keep
logs/in.gitignore. Never commit logs. - Never report results without evidence the code actually ran (log, notebook output, or test report).
6. Git
- Never include
Co-Authored-Byin commit messages.
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.
- 5d ago First seen · 48 lines · 426 tokens per session scan A fdc0f406a969
claude-academic-setup AGENTS.md is an instructions file published in the GitHub repository letitbk/claude-academic-setup (43 stars, last pushed 2mo ago), licensed MIT. It adds 426 tokens to every session, about $0.0021 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
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.