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/langerrr/zforge/template-conventionsnpx skills add Langerrr/zforge --skill template-conventionsgit clone --depth 1 https://github.com/Langerrr/zforgeWrote 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/skills/langerrr/zforge/template-conventions)<a href="https://agentmods.dev/skills/langerrr/zforge/template-conventions"><img src="https://agentmods.dev/badge/skills/langerrr/zforge/template-conventions.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.00107 | $0.01762 |
| Opus 5 | $0.00053 | $0.00881 |
| Sonnet 5 | $0.00021 | $0.00352 |
| Haiku 4.5 | $0.00011 | $0.00176 |
Grade A, and why
template-conventions 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 today.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zforge Template Conventions
Features are documented in docs/{feature_name}/, snake_case.
Core files
Always created by the zforge plan workflow:
| File | Owner | Purpose |
|---|---|---|
00_design_spec.md |
Planner | Problem, actors, requirements, boundary, acceptance vocabulary |
01_context.md |
Planner | Doc Map, key decisions, open questions with owner and method |
02_plan.md |
Planner | Technical plan, phase decomposition, Verification Matrix, environment assumptions, invariants |
discussion.md |
Planner | Reasoning generated during planning — written while thinking, not after |
decision_review.md |
Planner appends · user adjudicates | Decisions made without blocking, awaiting review |
05_progress_overview.md |
Planner only | Phase status, standing flags |
05_progress/05_XX_*.md |
One agent each | Per-phase contract, evidence, decisions, work log |
session_log.md |
Planner | Which sessions touched this feature, and how they ended |
Created when the feature needs them, never as empty placeholders:
| File | When |
|---|---|
| Core patterns doc | The feature changes data models, abstractions or architectural patterns. Without it agents follow the checklist and write structurally wrong code |
03_integration_summary.md, 04_integration_plan.md |
The plan spans backend and frontend |
07_harness_conventions.md |
A phase learns something about how the project is run and observed that a later phase would otherwise pay for again |
05_progress/review.md |
The zforge review workflow has findings |
06_post_deployment.md |
At completion |
08_configuration.md, 09_troubleshooting.md |
Config or gotchas emerge |
10_–12_refactor_* |
The task is a refactoring rather than a new feature |
.zforge-retro/*.md |
The zforge retro workflow is invoked |
Numbering
00–02 and the 05 family have fixed prefixes. Everything else is named for what it is and numbered by creation order in whatever slot is free — the name carries the identity, the number only sorts. Register every document in the Doc Map in 01_context.md with its purpose and which phases it binds.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +2 lines 5442416fcb81
- 4d ago First seen · 104 lines · 107 tokens per session scan A 282ae88d835b
template-conventions is a skill published in the GitHub repository Langerrr/zforge (10 stars, last pushed 3d ago), licensed MIT. It adds 107 tokens to every session and 1,762 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
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
skill-doc-sync
Post-ship doc sync across project markdown. Use when: sync docs, update docs, document changes, release notes.
add-native
Public entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps…
add-pdf-report
Internal implementation skill invoked by /add-native for app-generated PDF report workflows using expo-print and, when present, expo-sharing.
doc-review
Document review via Codex MCP. Use when: reviewing .md docs, tech spec audit, document quality check. Not for: code review (use codex-code-review), test review (use test-review). Output: 5-dimension rating table + gate.
handoff
Compacts the current conversation into one self-contained, tool-agnostic handoff document at docs/handoffs/ .md so any fresh agent or teammate can resume the work from that file alone. References pushed artifacts by path or URL, inlines anything not on the remote, and redacts secrets and PII. Re-running on an existing…