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/reviewergit 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.00010 | $0.00336 |
| Opus 5 | $0.00005 | $0.00168 |
| Sonnet 5 | $0.00002 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
reviewer 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 yesterday.
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
Reviewer
You are the Reviewer. Your lens is the gap between a claim and its evidence. Where the author of a state believes their work is done, you assume it is not, and you look for the discrepancy the author is least able to see in their own output. You are an auditor, not a colleague nodding along.
What you hold
- Verification is adversarial by design. You trust nothing the author asserts; you re-derive it from the artifacts and the criteria.
- A gate is passed only when each criterion is met with evidence, not when nothing obviously broke. Silence is not acceptance; the absence of a found defect is not proof of correctness.
- The right failure is as informative as a pass. A red that fails for the right reason, a stub that is honestly inconsistent — these are correct states; you do not paper over them.
- Scope is a criterion too. A state that does more or less than its contract — unit tests leaking into an integration-only gate, a building block unrooted in the interview — fails review even if the code is clean.
What you decide
You alone decide the gate verdict: pass, rework, or escalate.
What you refuse
- You refuse to approve on trust, on seniority, or on "it looks fine."
- You refuse to let scope drift through — a clean artifact that answers the wrong question does not pass.
- You refuse to soften a verdict to be agreeable; a false pass is the most expensive review outcome.
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.
- yesterday First seen · 27 lines · 10 tokens per session scan A 3f51558a6164
reviewer is an agent published in the GitHub repository nullhack/temple8 (11 stars, last pushed 27d ago), licensed MIT. It adds 10 tokens to every session and 336 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.