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/mr-devs/cc-academic-website/claude-mdgit clone --depth 1 https://github.com/mr-devs/cc-academic-websiteWrote 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/mr-devs/cc-academic-website/claude-md)<a href="https://agentmods.dev/instructions/mr-devs/cc-academic-website/claude-md"><img src="https://agentmods.dev/badge/instructions/mr-devs/cc-academic-website/claude-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.00555 | $0.00555 |
| Opus 5 | $0.00278 | $0.00278 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
cc-academic-website CLAUDE.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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Academic Website Template
A JSON-driven personal academic website: vanilla HTML/CSS/JS, no build step, deployable to GitHub Pages as-is.
Architecture (the one rule that matters)
Content lives in data/*.json, never in HTML. Each section of index.html is rendered client-side by a matching js/*.js module via the Site.load helper in js/utils.js. A section whose data file is missing, empty, or malformed hides itself silently.
| Section | Data file | Renderer |
|---|---|---|
| About/profile | data/profile.json |
js/profile.js |
| News | data/news.json |
js/news.js |
| Publications | data/publications.json |
js/publications.js |
| Working papers | data/working_papers.json |
js/working_papers.js |
| Ongoing projects | data/ongoing_projects.json |
js/ongoing_projects.js |
| Talks | data/talks.json |
js/talks.js |
| Software | data/software.json |
js/software.js |
| Teaching | data/teaching.json |
js/teaching.js |
Schemas are documented in .claude/skills/update-site-data/references/schemas.md. If you change a schema or renderer, update that file in the same session.
Conventions
- Entries in data files go newest-first; match each file's existing indentation.
- Local paths in data files use a
./prefix (e.g.,./docs/publications/...). - Per-paper assets live in
docs/publications/0_LastName_ShortTitle/(working papers) ordocs/publications/YYYY_LastName_ShortTitle/(published), each with acite.biband the PDF. - After editing any
data/*.json, validate it:python3 -m json.tool data/<file>.json.
Skills
/setup-site— design/build the site from reference URLs, screenshots, or design notes (initial setup or redesign)./update-site-data— add/convert papers, news, talks, software, projects, teaching, or profile edits./preview-site— validate data files, serve locally (python3 -m http.server), and verify sections render.
Preview
python3 -m http.server 8000 from the repo root, then open http://127.0.0.1:8000/. Opening index.html via file:// will NOT work — fetch needs HTTP.
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 · 38 lines · 555 tokens per session scan A 9a108c42076f
cc-academic-website CLAUDE.md is an instructions file published in the GitHub repository mr-devs/cc-academic-website (5 stars, last pushed 23d ago), licensed MIT. It adds 555 tokens to every session, about $0.0028 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.