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/markdown-contentgit 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/markdown-content)<a href="https://agentmods.dev/instructions/alshedivat/al-folio/markdown-content"><img src="https://agentmods.dev/badge/instructions/alshedivat/al-folio/markdown-content.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.00104 | $0.00104 |
| Opus 5 | $0.00052 | $0.00052 |
| Sonnet 5 | $0.00021 | $0.00021 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
al-folio markdown-content.instructions.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.
What it actually says
Markdown Content Instructions (v1.x)
Scope: _pages/**, _posts/**, _projects/**, _news/**, _teachings/**, _books/**
Guidance
- Keep starter content examples aligned with pluginized v1 behavior.
- Do not document runtime implementation details as starter-owned unless they truly are.
- When content depends on a plugin feature, ensure plugin wiring exists in
_config.ymlandGemfile.
Validation
Use the validated command set in AGENTS.md.
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 · 14 lines · 104 tokens per session scan A 79309de1a5cc
al-folio markdown-content.instructions.md is an instructions file published in the GitHub repository alshedivat/al-folio (16,083 stars, last pushed 3d ago), licensed MIT. It adds 104 tokens to every session, about $0.0005 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
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.
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.
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.