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 skills add nullhack/temple8 --skill select-build-targetgit clone --depth 1 https://github.com/nullhack/temple8Wrote 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/nullhack/temple8/select-build-target)<a href="https://agentmods.dev/skills/nullhack/temple8/select-build-target"><img src="https://agentmods.dev/badge/skills/nullhack/temple8/select-build-target/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nullhack/temple8/select-build-target"><img src="https://agentmods.dev/badge/skills/nullhack/temple8/select-build-target.svg" alt="Reviewed on agentmods" width="80" 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.00022 | $0.00367 |
| Opus 5.5 | $0.00009 | $0.00147 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
select-build-target 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 1mo 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
Select Build Target
- Load [[software-craft/tdd]], [[software-craft/docstring-lifecycle]], [[software-craft/git-conventions]] — the cycle, the docstring-free-source rule, and the branch model. Ensure the build runs on
feature/<session_id>: if absent, branch it off dev (git checkout -b feature/<session_id> dev); if it exists (resumed cycle), check it out. The contract surface was committed to dev at plan, so the branch starts from it. - Discover the backlog: collect tests carrying the pending marker (
uv run pytest --collect-only -m pending -q). Map each pending test to the source module it exercises. - Pick the lowest-layer contract that still has pending tests — layer order is dependency order, so a module is built only after the modules it imports are built.
- IF a shared or foundation module (shared data types with no dedicated external-boundary test of its own) is needed THEN pull it in and build it alongside the first contract that depends on it; record both.
- Treat the pending marker — not the presence of the source .py — as what makes a contract selectable: a reworked contract re-enters the queue even when its .py already exists. IF no pending tests remain anywhere THEN the system is built.
- IF the target module's .py already exists (rework) THEN strip it:
uv run python scripts/strip_docstrings.py <package>/<module>.py. Skip if absent (new contract). - Skim the target's .pyi and its tests for context, not the whole project.
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.
- 1mo ago First seen · 15 lines · 22 tokens per session scan A 3a3a0d1f8284
select-build-target is a skill published in the GitHub repository nullhack/temple8 (11 stars, last pushed 29d ago), licensed MIT. It adds 22 tokens to every session and 367 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
build-prs-from-tickets
Implement a planned scope of GitHub or GitLab issues with agents - each ticket is implemented in its own worktree, reviewed, tested, and opened as its own PR or MR. Use when the user says "execute tickets", "implement the tickets for scope", "run the scope", or "build-prs-from-tickets ".
build-tickets-from-feature
Break agreed work into small, dependency-ordered tickets and create them as GitHub or GitLab issues. Use when the user says "plan this feature", "break this into tickets", "create tickets for", or "plan the implementation of".
uv-docs
Astral uv 0.11.x — fast Python package and project manager in Rust. Projects, scripts, tools, Python versions, pip interface.
aip-tracker
Track Airflow Improvement Proposal (AIP) implementation progress by comparing Confluence specs against codebase evidence. Use when asked to assess, report on, or compare AIP status.
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
intake
Inspect configured Sources and propose evidence-backed Backlog work.