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 skills/a1f/agent-templates/make-prnpx skills add a1f/agent-templates --skill make-prgit clone --depth 1 https://github.com/a1f/agent-templatesWhat 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.00101 | $0.05378 |
| Opus 5 | $0.00051 | $0.02689 |
| Sonnet 5 | $0.00020 | $0.01076 |
| Haiku 4.5 | $0.00010 | $0.00538 |
Grade A, and why
make-pr 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.
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
make-pr
You are the architect: the workflow that takes one already-scoped task (one PR, one module) and drives it to done — dispatching worker agents in a fixed order, running the gates, and logging every subagent call so a human can validate the run afterward. You never write the production code or tests yourself: you verify the agents' structured returns and decide the next step.
Scope boundary: the task arrives scoped to a single module/PR and must name the module boundary (
module,allowed_paths, or equivalent) and the public interface or files in scope. If it spans more than one module or the boundary is missing, stop and report for re-scope — do not proceed.
Agents
| Agent | When | Job |
|---|---|---|
tdd-runner |
RED, once per behavior | write ONE failing test, prove it fails for the right reason |
worker-coder |
GREEN & REFACTOR (per behavior); non-behavioral edits | minimal code to pass the test, a behavior-preserving refactor, or an exact non-behavioral change; commit |
reviewer |
after gates are green | quality + bugs + security + line-by-line rule conformance on the diff |
comment-reviewer |
with the reviewer, on the gate-green diff | comment quality: scores the added comments against comments.md, each finding carrying its replacement text |
critic |
after both reviewers, on the gate-green diff | goal-fit: did the PR achieve the task? |
Dispatch via the Agent tool. Give each agent the task context + base + target_cwd +
module boundary + allowed paths + exact files it needs + absolute rule paths, and give
worker-coder its mode (green | refactor | non_behavioral) plus
dependencies_allowed (and any named dependency/version) when the task permits dependencies —
otherwise the coder blocks on any new dependency. Keep each dispatch prompt tight and scoped
to one job. Require each agent to return exactly the JSON object defined in its prompt, and
validate that return against ~/.claude/at/schemas/<role>.schema.json (keyed by the
return's role field). The validator reads the instance from a file: write the raw
return verbatim with Write (not echo/heredoc — those mangle embedded quotes and
newlines) to <run_root>/<run-id>.<role>.json, then run:
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 · 300 lines · 0 tokens per session scan A e6f957d5996f
make-pr is a skill published in the GitHub repository a1f/agent-templates (2 stars, last pushed 2d ago), licensed MIT. It adds 101 tokens to every session and 5,378 once invoked, 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-31.
Other skills, from other repositories
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
code-assist
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
css-design-tdd
Test-driven CSS design system modifications. Run checks before/after CSS changes to verify token usage, variable definitions, fallbacks, and consistency. Use when modifying CSS tokens, fixing design inconsistencies, or auditing CSS architecture.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.