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 commands/mtthsnc/tempest/office-hoursgit clone --depth 1 https://github.com/mtthsnc/tempestWrote 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/commands/mtthsnc/tempest/office-hours)<a href="https://agentmods.dev/commands/mtthsnc/tempest/office-hours"><img src="https://agentmods.dev/badge/commands/mtthsnc/tempest/office-hours.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00116 |
| Opus 5 | $0.00006 | $0.00058 |
| Sonnet 5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
office-hours 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 3d 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
Load and follow the office-hours skill to pressure-test an idea before any planning begins.
Idea or feature request: $ARGUMENTS
Work through the skill's procedure end to end: restate the request, run the forcing questions, and
sharpen the answers into a tightened problem statement with explicit scope boundaries. Do not design
or plan here — hand the sharpened brief to the plan workflow when done.
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.
- 3d ago First seen · 12 lines · 13 tokens per session scan A 96d9bbcc3a07
office-hours is a command published in the GitHub repository mtthsnc/tempest (2 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 116 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-31.
Other commands, from other repositories
factory-tune
Review factory performance and propose deliberate constraint changes - tighten where a gate let something through, loosen where a class of change has been green long enough.
remote
Start, stop, restart, inspect, or troubleshoot the local NordRelay process.
service
Install, remove, or inspect OS service integration.
foreground
Run the connector in the current terminal.
stop
Stop the connector and WebUI processes managed by NordRelay.
quiz-me
Quiz me using the coding-tutor skill.