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/nullhack/temple8/merge-to-devnpx skills add nullhack/temple8 --skill merge-to-devgit 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.00031 | $0.00367 |
| Opus 5 | $0.00015 | $0.00183 |
| Sonnet 5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
merge-to-dev 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
Merge To Dev
- Load [[software-craft/git-conventions]], [[software-craft/docstring-lifecycle]] — squash-merge form and the docstring lifecycle.
- Switch to dev and squash-merge the feature branch (
feature/<session_id>) per [[software-craft/git-conventions]]; the green-suite and whole-suite stubtest gate is verified on dev after the merge. Delete the merged branch (git branch -d feature/<session_id>) — no dangling branches. - Verify the full suite is green on dev after the merge: no pending markers remain (every source .pyi has its sibling .py, so every test runs) and every test passes.
- Verify whole-suite stubtest is clean across both source and tests: every source .pyi and every test .pyi agrees with its sibling .py — no drift smuggled in by the batch.
- Regenerate docstrings for the public surface of every contract shipped this cycle (modules, classes, public functions and methods) — faithful prose from the stable code, never a mechanical restatement of the signature; the why of an architectural decision lives in an ADR, not a docstring. Per [[software-craft/docstring-lifecycle]].
- Run
task lint-merge— addsSIMandRUFto the dev select and runsruff format .— so restructure and format land on dev exactly once per merge, never during build. - Commit the regenerated docstrings and the format pass on dev as
docs(<scope>): regenerate docstrings + format.
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 · 15 lines · 31 tokens per session scan A 0cb216fcb0d0
merge-to-dev is a skill published in the GitHub repository nullhack/temple8 (11 stars, last pushed 28d ago), licensed MIT. It adds 31 tokens to every session and 367 once invoked, about $0.0002 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 skills, from other repositories
docs-sync
Detect user-visible changes from the last 24h of commits on main and propose doc and scenario updates as PRs.
conventional-commit
Draft a Conventional Commit message when the user requests a commit or message. Formats only; does not authorize Git operations.
keel-autopilot
Gated autonomy for one session — advance phases back-to-back with the full /keel-phase-review run at every gate, auto-commit at phase ends, batch pushes for ONE approval. Stops on gate FAIL, UNCERTAIN decisions, architecture surprises, or security-adjacent changes. Push is never automatic. Solo sessions or an agent…
scope-guard
Judgment check before calling substantial work done or proposing a commit. Use before "done", before committing more than a trivial change, and whenever you notice yourself building something nobody asked for. The judgment layer above the automated gates, not a duplicate of them.
git-precommit
Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送, stage, 暫存, checkin, 簽入, submit, save, 準備發布, ready to commit, 要推了.
git-doc-updater
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布, documentation, 同步文件, 文件檢查, doc check, 發布前, before release, 準備發布.