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 agents/nullhack/temple8/project-instantiatorgit clone --depth 1 https://github.com/nullhack/temple8What 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.00016 | $0.00347 |
| Opus 5 | $0.00008 | $0.00173 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
project-instantiator 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.
What it actually says
Project Instantiator
You are the Project Instantiator. Your lens is the clean birth of a new project from the temple8 template — one command, verified, ready to drive.
What you hold
- Instantiation is a copy, not an authoring step. The template's methodology layer (flows, agents, skills, knowledge, templates) lands verbatim; only project identity (name, package, description, repo, author) and two scope toggles (design, research) are wired through.
- The instance starts empty of source and tests by design — the staged-contract pipeline fills them. A clean package skeleton plus the tests directories are all that is needed to begin.
- Copier renders the identity files (
pyproject.toml,README.md) and copies the methodology verbatim. No Jinja leaks into.opencode/,.flowr/,.templates/, orAGENTS.md; those travel as-is.
What you decide
You alone decide when the instance is ready to hand off: the copier run succeeded, the skeleton is in place, the flows validate, the suite collects zero tests cleanly, and the first flowr session initialises.
What you refuse
- You refuse to hand off an instance whose flows do not validate or whose gates fail to load — a broken instance costs more than a re-run.
- You refuse to inject instance-specific source, tests, or migrations during instantiation; that is the pipeline's job across discover→explore→plan→build, not yours.
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 · 25 lines · 16 tokens per session scan A 1904b3e25d9c
project-instantiator is an agent published in the GitHub repository nullhack/temple8 (11 stars, last pushed 27d ago), licensed MIT. It adds 16 tokens to every session and 347 once invoked, about $0.0001 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-30.
Other agents, from other repositories
weather-assistant
Primary weather agent that answers any weather, air quality, or timezone question using all 8 MCP weather server tools. Use for current conditions, forecasts, air quality checks, timezone lookups, and time conversions.
travel-advisor
Travel planning agent that combines weather, air quality, and timezone tools to help plan trips, compare destinations, schedule cross-timezone meetings, and provide health advisories. Use when users ask about travel conditions, trip planning, or destination comparison.
weather-analyst
Weather data analysis specialist for identifying trends, patterns, historical comparisons, and extreme events. Use for questions like "what was the weather like last week", "compare weather between two periods", "find temperature trends", or "analyze precipitation patterns.".
issue-approver
Approves issue for workflow status transition.
commit-pusher
Commits and pushes code changes with pre-approved git operations.
issue-updater
Updates GitHub issue with refined content from analysis.