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/d-o-hub/github-template-ai-agents/agents-mdgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/agents-md)<a href="https://agentmods.dev/instructions/d-o-hub/github-template-ai-agents/agents-md"><img src="https://agentmods.dev/badge/instructions/d-o-hub/github-template-ai-agents/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 | $0.02401 | $0.02401 |
| Opus 5 | $0.01201 | $0.01201 |
| Sonnet 5 | $0.00480 | $0.00480 |
| Haiku 4.5 | $0.00240 | $0.00240 |
Grade A, and why
github-template-ai-agents AGENTS.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 yesterday.
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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Named Constants
# File size limits (lines)
readonly MAX_LINES_PER_SOURCE_FILE=500
readonly MAX_LINES_PER_SKILL_MD=250
readonly MAX_LINES_AGENTS_MD=200
# Retry and polling configuration
readonly DEFAULT_MAX_RETRIES=3
readonly DEFAULT_RETRY_DELAY_SECONDS=5
readonly DEFAULT_POLL_INTERVAL_SECONDS=5
readonly DEFAULT_MAX_POLL_ATTEMPTS=12
readonly DEFAULT_TIMEOUT_SECONDS=1800
# Git/PR configuration
readonly MAX_COMMIT_SUBJECT_LENGTH=150
readonly MAX_PR_TITLE_LENGTH=150
readonly MAX_PR_BODY_LENGTH=1000
Process modes
| Mode | When | Required steps |
|---|---|---|
| Light (default for adopters) | Small fixes, docs, single-skill work | Quality gate → atomic commit → PR |
| Full (template / large changes) | Architecture, multi-file refactors, new subsystems | GOAP + ADR + TRIZ phases below |
See agents-docs/ADOPTION_PROFILES.md for minimal vs full template surface area.
Profile scoping: This file documents the template's Full (maintainer) surface. Adopters on Light mode should treat Metrics, DORA, CI-status gating, ADR/GOAP/TRIZ, and template-generated-document checks as optional — see
agents-docs/ADOPTION_PROFILES.mdfor what to keep vs. prune.
Development Phases (full mode)
Use GOAP + ADRs + TRIZ for structured development when the change is non-trivial.
Prerequisites:
- Fetch/pull latest default remote branch before beginning.
- Check CI Status: Agents MUST check
.github/ci-status/ci-status.json. If NOT "passing", pause until fixed.
-
ANALYZE & STRATEGIZE (Phase 1)
- Action: Use
triz-analysisortriz-solver. Write an ADR inplans/. - Human Gate: Review and approve the ADR and analysis before proceeding. Only human gate.
- Action: Use
-
DECOMPOSE & PLAN (Phase 2)
- Action: Use the
goap-agentto break down inplans/GOAP_STATE.md(create if missing).
- Action: Use the
-
EXECUTE & COORDINATE (Phase 3)
- Action: Execute tasks systematically using atomic commit workflow.
- Action: Use
git-github-workflowor run./scripts/self-fix-loop.shuntil all CI checks pass.
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.
- yesterday First seen · 194 lines · 2,401 tokens per session scan A d792cae03388
github-template-ai-agents AGENTS.md is an instructions file published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed today), licensed MIT. It adds 2,401 tokens to every session, about $0.0120 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-09-03.
Other instructions, from other repositories
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.