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/docxology/template/agents-mdgit clone --depth 1 https://github.com/docxology/templateWhat 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.17938 | $0.17938 |
| Opus 5 | $0.08969 | $0.08969 |
| Sonnet 5 | $0.03588 | $0.03588 |
| Haiku 4.5 | $0.01794 | $0.01794 |
Grade D, and why
template AGENTS.md scanned grade D with 4 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo tlmgr update --self Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
remove the stale env entirely: `rm -rf projects/{name}/.venv` (it is regenerated on demand; Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
with patch('requests.post') as mock_post: Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( How it starts
The opening of the file, as written. The whole thing — 1,564 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🤖 AGENTS.md - System Documentation
🎯 System Overview
This document provides documentation for the Research Project Template system, ensuring understanding of all functionality, configuration options, and operational procedures.
📄 Publication
Title: A template/ approach to Reproducible Generative Research: Architecture and Ergonomics from Configuration through Publication DOI: 10.5281/zenodo.19139090 · Record: zenodo.org/records/19139090
template/ applies Infrastructure as Code to the research lifecycle: version-controlled manuscripts, tests, provenance, and a declared pipeline DAG. Layer 1 (infrastructure/) is separated from Layer 2 (self-contained projects under projects/). Current measured counts and stage facts live in docs/_generated/COUNTS.md; re-derive them instead of copying literals into prose. Each directory carries README.md + AGENTS.md; infrastructure packages usually add SKILL.md for agent routing. Full paper, metrics, and claims: Zenodo record above and root README.md.
Documentation map
| Entry | Role |
|---|---|
README.md |
Onboarding, documentation hub links, exemplar table |
.cursorrules |
Cursor agents: layer rules, CI scope, editing discipline |
CLAUDE.md |
Command cheat sheet, patterns; keep in sync with this file for pipeline wording |
This file (AGENTS.md) |
Full reference: stages, validation, modules, troubleshooting |
docs/documentation-index.md |
Flat index of long-lived docs |
docs/_generated/active_projects.md |
Authoritative public CI/documentation project names — never hard-code rotating private paths in docs |
docs/_generated/COUNTS.md |
Measured coverage and counts; refresh after changing gates or discovery |
.github/README.md |
GitHub: CI overview, templates, Dependabot |
.github/AGENTS.md |
Actions job names, coverage gates, local reproduction commands |
TO-DO.md |
Current backlog, scoped by acceptance line |
CHANGELOG.md |
Release history |
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 · 1,564 lines · 17,938 tokens per session scan D c747c2e415e0
template AGENTS.md is an instructions file published in the GitHub repository docxology/template (19 stars, last pushed 2d ago), licensed Apache-2.0. It adds 17,938 tokens to every session, about $0.0897 per session on Opus 5. A static security scan graded it D with 4 findings (asks for root, recursive force delete, 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
LynxPrompt CLAUDE.md
Instructions for GeiserX/LynxPrompt, covering claude.md - ai agent instructions for lynxprompt, 🚀 release process (critical - read carefully), understanding the release pipeline, step-by-step release process and 1. switch to develop branch.
domain-experts AGENTS.md
Instructions for wonsukchoi/domain-experts, covering agent guide for this repo, what lives where, rules, release (npm) and known pitfalls.
domain-experts CLAUDE.md
Instructions for wonsukchoi/domain-experts, covering domain experts — session bootstrap, non-negotiables when adding or editing roles, dual-graph context policy, mandatory: always follow this order and token usage.
karpathy-interaction-guidelines AGENTS.md
Instructions for hburaktasyurek/karpathy-interaction-guidelines, covering interaction guidelines, 1. think before acting, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
talisman-skill AGENTS.md
Instructions for jeunecraack/talisman-skill, covering talisman — agent playbook (v1), when to run, workflow (8 phases), key features and repo structure.
trellis AGENTS.md
Instructions for craigcossairt/trellis, covering agents.md , project, what i need from agents, current state - source of truth pointers and tech stack.