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/atebites-hub/pjtemplate/agents-mdgit clone --depth 1 https://github.com/atebites-hub/PJTemplateWrote 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/atebites-hub/pjtemplate/agents-md)<a href="https://agentmods.dev/instructions/atebites-hub/pjtemplate/agents-md"><img src="https://agentmods.dev/badge/instructions/atebites-hub/pjtemplate/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.05384 | $0.05384 |
| Opus 5 | $0.02692 | $0.02692 |
| Sonnet 5 | $0.01077 | $0.01077 |
| Haiku 4.5 | $0.00538 | $0.00538 |
Grade A, and why
PJTemplate 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Project Rules
Guidelines for Filling Out This Template
- Start with
docs/agents/template_setup_checklist.md— it is the exhaustive manifest of every feature/decision this template ships, and it drives the setup gate (scripts/check-template-setup.sh) that blocks commits until the scaffold is fully transformed. Step 1 isrm .template-scaffold(activates the gate); record every decision inconfig/setup.toml. - Replace [Project Name] with your project's name (e.g., "My API Service" or "Game App").
- Set [Number] to the count of core docs (default 10; adjust if needed).
- Customize consultation/quality gates for your domain (e.g., add "API rate limits" for server-heavy projects).
- For multi-agent use: Ensure links work across tools (e.g., mdc: for Markdown previews); test in Cursor/Claude.
- Reference repo structure: Store this as root/AGENTS.md; link to /file_structure.md for agent file impacts.
- When transforming this template repository into the user's desired repository, first consult with the user in detail their project requirements.
- For each template file being updated, iterate in detail with the user over each section, ensuring that the document matches the user's preferences.
Memory System
Task memory tracking is handled by the memory-system skill. See .agents/skills/memory-system/SKILL.md for workflow.
Requirement: Sprint tasks live in docs/agents/implementation_plan.md. That a task memory accompanies source changes — with its reasoning fields filled — is enforced by scripts/check-task-compliance.sh (checks C1/C3) via the git pre-commit hook and CI, not by prose. See docs/agents/enforcement_matrix.md.
Reasoning System
Structured reasoning before implementation is handled by the reasoning-system skill. See .agents/skills/reasoning-system/SKILL.md for workflow and bindings.
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.
- 3d ago First seen · 294 lines · 5,384 tokens per session scan A 91f4fa385e35
PJTemplate AGENTS.md is an instructions file published in the GitHub repository atebites-hub/PJTemplate (2 stars, last pushed 11d ago), licensed MIT. It adds 5,384 tokens to every session, about $0.0269 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.