template_setup_checklist

A checklist and setup gate for turning a project template into a real project. The gate checks required changes and can block commits until setup decisions and confirmations are recorded.

In plain words
What is it for?
Use it to activate project setup checks, replace template placeholders, run the setup process, and verify required decisions before committing.
Why use it?
It reduces the chance of committing an unfinished template with placeholder names or missing setup work.

Agent

Install

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.

agentmods
npx agentmods add agents/atebites-hub/pjtemplate/template_setup_checklist
Clone the repo
git clone --depth 1 https://github.com/atebites-hub/PJTemplate
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,618 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03618
Opus 5 $0.00000 $0.01809
Sonnet 5 $0.00000 $0.00724
Haiku 4.5 $0.00000 $0.00362

Measured yesterday against content hash a190e2556e78, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

template_setup_checklist 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.

docs/agents/template_setup_checklist.md · 253 lines

How it starts

The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Template Setup Checklist

Purpose. This is the canonical, exhaustive manifest for transforming the PJTemplate scaffold into a real project. Every feature the template ships is listed below as an explicit decision or action. Work top to bottom. The setup gate (scripts/check-template-setup.sh, wired into the pre-commit hook) blocks commits until the 🔒 items pass and the ✍️ attestations in config/setup.toml are filled.

Lock icons: 🔒 = auto-verified by the gate · ✍️ = an attestation you record in config/setup.toml (the gate cannot read your intent) · 🗑️ = delete if you chose strip.


0. Activate the gate

  • 🔒 Delete the marker to turn the gate on: rm .template-scaffold (while the marker exists the gate is dormant — the pristine template).
  • Run ./scripts/setup.sh — installs pyenv, Python, venv, hash-pinned deps, activates git hooks, and builds ODW if Node ≥ 20 is present.

1. Identity & placeholders 🔒

Every literal below is scanned across tracked text files (template docs about the template are excluded). Replace all occurrences project-wide.

  • 🔒 [Project Name] / [Project name] → your project name (README, AGENTS.md).
  • 🔒 [Number] → count of core docs (AGENTS.md "Guidelines" section).
  • 🔒 yourapp → your slug. Files: pyproject.toml (name), config/defaults.toml (app.name, observability.service_name, metrics.namespace, fastapi.title), config/infra/grafana/ (provisioning/dashboards/dashboards.yaml, dashboards/json/*.json), config/infra/alloy/config.alloy (service relabel). (Note: config/infra/prometheus/prometheus.yml has no yourapp literal — Prometheus job names come from Alloy's relabeling, so there is nothing to edit there.)
  • 🔒 YourApp / Your Name → author (e.g. pyproject.toml authors).
  • 🔒 PJTemplate / pjtemplate → any remaining repo-name references.
  • 🔒 README placeholders: [Brief ...], [repo-url], [License: ...], [type: ...], plus the two inside the overview block — [core purpose], [key tech] — and [e.g., ...] (Assumptions / Known Issues on line 51).
  • 🔒 Coverage floor --cov-fail-under=080 in pyproject.toml ([tool.pytest.ini_options] addopts).

Read the full file on GitHub · 253 lines

Changes

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.

  1. yesterday First seen · 253 lines · 0 tokens per session scan A a190e2556e78

Subscribe to this mod's changes

template_setup_checklist is an agent published in the GitHub repository atebites-hub/PJTemplate (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,618 tokens. 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.