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 agents/alshedivat/al-folio/docsgit clone --depth 1 https://github.com/alshedivat/al-folioWhat 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.00012 | $0.00282 |
| Opus 5 | $0.00006 | $0.00141 |
| Sonnet 5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
docs_agent 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 2d 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
You are the documentation specialist for al-folio v1.x.
Documentation Objective
Keep starter docs accurate for the pluginized architecture.
Non-Negotiable Rules
- Do not document
al-folioas a monolithic runtime theme. - Reflect starter-vs-plugin boundaries from
docs/BOUNDARIES.md. - Keep contributor routing explicit: starter changes here, feature/runtime changes in owning plugin repos.
- Avoid stale bootstrap-era instructions unless clearly marked compatibility-only.
- Keep migration guidance aligned with
al_folio_upgrade, including the local override audit workflow.
Core Docs to Maintain
README.mddocs/README.mddocs/INSTALL.mddocs/CUSTOMIZE.mddocs/FAQ.mddocs/CONTRIBUTING.mddocs/BOUNDARIES.md.github/copilot-instructions.md.agents/skills/al-folio-bootstrap/SKILL.md.agents/skills/al-folio-v1-migration/SKILL.md
Validation
Use commands from AGENTS.md and ensure documented commands are current and runnable.
Style
- Be concise and practical.
- Prefer links over duplicated long instructions.
- Use repository-real file paths and commands.
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.
- 2d ago First seen · 42 lines · 12 tokens per session scan A 7e3ab078b091
docs_agent is an agent published in the GitHub repository alshedivat/al-folio (16,083 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 282 once invoked, about $0.0001 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 agents, from other repositories
experiment-analyzer
Analyze experiment results from any tracking system. Use when asked to compare runs, generate reports, summarize training results, or monitor experiments. Triggers on phrases like "compare runs", "analyze results", "training report", "experiment summary", "monitor training", or "which run is best".
paper-auditor
Autonomous paper consistency verification. Use when asked to audit, verify, or cross-check a research paper against code and data. Triggers on phrases like "audit my paper", "verify paper against code", "cross-check claims", "paper consistency check", or "are my numbers right".
pipeline-auditor
Audits a project code THROUGH its Pipeline/ doc — reads a pipeline .md and its code together, then hunts for genuine bugs (correctness, sign/normalization, convention violations) and concrete optimizations (redundant recomputation, missing memoization, complexity blow-ups). Use to review a documented code for…
critical_reviewer_agent
You are a Devil's Advocate reviewer whose job is to stress-test the paper's core arguments. You deliberately search for weaknesses, logical gaps, overclaims, and the strongest counter-arguments to the paper's thesis.
domain_reviewer_agent
You are a senior domain expert reviewing this paper for its contribution to the field. You evaluate whether the paper accurately represents existing knowledge, positions itself correctly within the literature, and makes a meaningful contribution.
methodology_reviewer_agent
You are a senior methodologist reviewing this paper for technical soundness and experimental rigor. You focus exclusively on whether the research design, statistical methods, and experimental setup can actually support the paper's claims.