al-folio is a Jekyll starter for building academic websites, personal sites, and portfolios. It is used by academics who want a responsive site based on independently versioned plugin components.
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/alshedivat/al-folio/agents-mdgit clone --depth 1 https://github.com/alshedivat/al-folioWrote 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/alshedivat/al-folio/agents-md)<a href="https://agentmods.dev/instructions/alshedivat/al-folio/agents-md"><img src="https://agentmods.dev/badge/instructions/alshedivat/al-folio/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.1 | $0.01545 | $0.01545 |
| Opus 5 | $0.00772 | $0.00772 |
| Sonnet 5 | $0.00309 | $0.00309 |
| Haiku 4.5 | $0.00154 | $0.00154 |
Grade A, and why
al-folio AGENTS.md scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS http://127.0.0.1:8080/al-folio/ >/dev/null How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines for al-folio (v1.x)
This file is the authoritative entry point for coding agents working in this repo. Read it before making any change. It is intentionally short and tool-neutral; it links to the one place each longer-form fact lives.
al-folio v1.x is a thin Jekyll starter, not a theme. This repo owns starter wiring, example content, docs, and cross-plugin tests. All runtime — layouts, includes, Sass, Liquid tags, filters, feature JS — lives in versioned gems published under al-org-dev.
Route your change
Find your change on the left; edit only what is on the right.
| Your change | Goes in |
|---|---|
| Dependency pin, plugin activation, feature flag | this repo: Gemfile and _config.yml (both — see below) |
| Example/demo content, bibliography, data files | this repo: _pages, _posts, _projects, _news, _teachings, _books, _data |
| Documentation | this repo: docs/ (long-form) or this file (agent rules) |
| Cross-plugin integration test, visual parity test | this repo: test/integration_*.sh, test/visual/ |
| Plugin catalog metadata | this repo: _data/featured_plugins.yml |
| A layout, include, or Sass partial | the owning gem — start with al_folio_core |
| A Liquid tag or filter, or what a tag renders | the gem that registers it — see the delegation table |
| Feature behavior (search, math, charts, comments, cookies, icons, CV, distill, analytics, images, newsletter, citations) | that feature's gem — see docs/BOUNDARIES.md |
| Component/unit test for gem-owned behavior | the owning gem, not here |
| A feature with no existing owner | open a plugin proposal issue first, then a standalone plugin repo |
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.
- 6d ago First seen · 92 lines · 1,545 tokens per session scan A 1517d458104f
al-folio AGENTS.md is an instructions file published in the GitHub repository alshedivat/al-folio (16,089 stars, last pushed 5d ago), licensed MIT. It adds 1,545 tokens to every session, about $0.0077 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
sagarshah.dev AGENTS.md
Instructions for shahsagarm/sagarshah.dev, covering this is not the next.js you know, sagarshah.dev v2, commands, token contract (strongest rule in the repo) and architecture.
website AGENTS.md
AGENTS.md instructions for rimzzlabs/website, covering agents.md, commands, stack, structure and conventions.
website CLAUDE.md
Claude Code instructions for rimzzlabs/website: See AGENTS.md — the single source of truth for conventions, commands, architecture, and gotchas in this repo.
academic-homepage-cv-sync AGENTS.md
AGENTS.md instructions for kw1jjang/academic-homepage-cv-sync, covering project notes, what this repo is, prerequisites, cv ↔ website sync and workflow.
sagarshah.dev CLAUDE.md
Instructions for shahsagarm/sagarshah.dev: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
academic-homepage-cv-sync CLAUDE.md
Claude Code instructions for kw1jjang/academic-homepage-cv-sync: See AGENTS.md — the instructions live there so that every coding agent reads the same file. Read it before editing anything in this repo.