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/pueraeternis/agentic-project-template/repository-initializationnpx skills add pueraeternis/agentic-project-template --skill repository-initializationgit clone --depth 1 https://github.com/pueraeternis/agentic-project-templateWrote 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/pueraeternis/agentic-project-template/repository-initialization)<a href="https://agentmods.dev/skills/pueraeternis/agentic-project-template/repository-initialization"><img src="https://agentmods.dev/badge/skills/pueraeternis/agentic-project-template/repository-initialization.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.1 | $0.00000 | $0.00804 |
| Opus 5 | $0.00000 | $0.00402 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
repository-initialization 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 5d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Initialization
Purpose
This skill transforms approved project documentation into a repository that is ready for implementation.
Repository Initialization does not design or implement the project.
Instead, it materializes the approved project and engineering decisions into a consistent repository structure.
The result is a repository ready for the first implementation plan.
Lifecycle Stage
Project Discovery
↓
Roadmap Creation
↓
Architecture Design
↓
Engineering Design
↓
Repository Initialization
↓
Plan Creation
Repository Initialization is the bridge between project design and implementation.
Role
Primary role:
Initialization Agent
When to Use
Use this skill when:
PROJECT.mdhas been approved;ROADMAP.mdhas been approved;ARCHITECTURE.mdhas been approved;ENGINEERING.mdhas been approved;- a new project repository is being initialized.
Normally this skill is executed once.
It may later be executed again to synchronize repository metadata without modifying implementation artifacts.
Do not use this skill for:
- architecture design;
- engineering design;
- implementation planning;
- production code;
- dependency installation;
- runtime bootstrap.
Inputs
Required:
PROJECT.mdROADMAP.mdARCHITECTURE.mdENGINEERING.md
Additional inputs:
- framework templates;
- framework rules;
- repository skeleton.
Repository Initialization must never invent missing project decisions.
Outputs
Produce an initialized repository by:
- generating project documentation from templates;
- generating project-local Cursor configuration;
- generating project-local Codex configuration;
- generating operational documentation;
- synchronizing repository metadata;
- validating repository structure.
No production source code should be generated.
Procedure
Step 1 — Validate Project Design
Verify that all required project documentation exists and is approved:
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.
- 5d ago First seen · 236 lines · 0 tokens per session scan A 3a238e4b513b
repository-initialization is a skill published in the GitHub repository pueraeternis/agentic-project-template (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 804 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.
Other skills, from other repositories
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.