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.
git clone --depth 1 https://github.com/Kastalien-Research/thoughtboxWrote 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/kastalien-research/thoughtbox/validate-brief)<a href="https://agentmods.dev/commands/kastalien-research/thoughtbox/validate-brief"><img src="https://agentmods.dev/badge/commands/kastalien-research/thoughtbox/validate-brief/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/commands/kastalien-research/thoughtbox/validate-brief"><img src="https://agentmods.dev/badge/commands/kastalien-research/thoughtbox/validate-brief.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.00006 | $0.00247 |
| Opus 5.5 | $0.00002 | $0.00099 |
| Sonnet 5.5 | $0.00001 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
hdd-validate-brief 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
HDD Validate Module
Inputs
task_goalpaths_to_inspectacceptance_checkstest_targetsstaging_adr_path
Steps
- Run automated checks relevant to hypothesis outcomes.
- Capture pass/fail evidence per hypothesis.
- Request manual verification checkpoints when required.
- Classify each hypothesis: validated, falsified, or inconclusive.
- Produce a validation report with evidence references.
Outputs
statussummaryartifactsopen_riskshypothesis_results
Stop Conditions
- Success: every hypothesis has an explicit outcome.
- Failure: insufficient evidence to classify outcomes.
- Escalation: manual test requirement cannot be completed.
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 · 43 lines · 6 tokens per session scan A 24c48a734f09
hdd-validate-brief is a command published in the GitHub repository Kastalien-Research/thoughtbox (66 stars, last pushed 3mo ago), licensed MIT. It adds 6 tokens to every session and 247 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
apex
APEX Methodology - The systematic Analyze-Plan-Execute-eLicit-eXamine approach for intelligent development. Reduces hallucination and defect risk through mandatory parallel research, self-review, and validation gates.
test-prompt
Test an AI prompt against multiple scenarios to verify consistent, quality output.
complete
Complete a partially implemented feature by filling gaps and ensuring production readiness.
test
Test commit. Use for add tests, update tests, test coverage, unit test, spec.
run-e2e
Run end-to-end tests against the application using Playwright or Cypress.
test
Generate tests for the specified code or feature.