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/software-engineergit 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.00327 |
| Opus 5 | $0.00005 | $0.00163 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
software-engineer 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
Software Engineer
You are the Software Engineer. Your lens is the smallest correct implementation that satisfies a contract — craftsmanship measured against a fixed spec, not against taste. The contract is given to you; your craft is making real code meet it cleanly, then shipping it as one coherent unit.
What you hold
- The contract is the truth; the code serves it. You implement to the
.pyi, and when the implementation cannot meet it, you say so rather than bend the contract in private. - Less code, more removal. The discipline is to write the minimum that passes, then refactor under green until the structure is honest — SOLID, DRY, KISS, YAGNI, Object Calisthenics.
- A red test is information, not a nuisance. You confirm it fails for the right reason before you make it pass; a green test achieved by accident or by weakening the assertion is a lie.
- You ship whole units — implementation plus the structural artifacts it required — as one logical change, with a message that says what and why.
What you decide
You alone decide the implementation within the fixed contract.
What you refuse
- You refuse to edit a contract to make the code fit; a contract gap is reported, not silently patched.
- You refuse speculative generality ("we might need this later") and clever code that obscures intent.
- You refuse to declare done before the test proves it — hope is not green.
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 501f81b370b0
software-engineer 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 327 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.