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 skills add Kastalien-Research/thoughtbox --skill thoughtbox-researchgit 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/skills/kastalien-research/thoughtbox/thoughtbox-research)<a href="https://agentmods.dev/skills/kastalien-research/thoughtbox/thoughtbox-research"><img src="https://agentmods.dev/badge/skills/kastalien-research/thoughtbox/thoughtbox-research.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01417 |
| Opus 5 | $0.00026 | $0.00709 |
| Sonnet 5 | $0.00010 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
thoughtbox:research 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research this topic using Thoughtbox IRCoT: $ARGUMENTS
Protocol References
- Cipher notation for long sessions:
thoughtbox://cipher - IRCoT pattern background:
thoughtbox://interleaved/research
Phase 1: Setup
Create a Thoughtbox session and assess available tools.
// thoughtbox_execute
async () => {
await tb.thought({
thought: "Research question: $ARGUMENTS. Available search tools: [list from ToolSearch]. Strategy: breadth-first scan, then depth on promising leads.",
thoughtType: "context_snapshot",
nextThoughtNeeded: true,
thoughtNumber: 1,
totalThoughts: 30,
sessionTitle: "Research: $ARGUMENTS",
sessionTags: ["research"],
contextData: {
toolsAvailable: [],
constraints: ["primary sources preferred"]
}
});
}
Steps:
- Use ToolSearch to discover available search tools (Exa, WebSearch, WebFetch, Grep, Read).
- Record thought 1 as
context_snapshot: state the research question, available tools, constraints. - If no search tools are available, note the limitation and rely on codebase/knowledge graph only.
Phase 2: IRCoT Loop (Think, Search, Integrate, Repeat)
Run this cycle until the question is answered or no productive search avenues remain.
2a: Reason
Record a reasoning thought: what do I need to find out next? What gaps remain?
// thoughtbox_execute
async () => {
await tb.thought({
thought: "Gap: I know X but not Y. Next search: [specific query]. Rationale: [why this fills the gap].",
thoughtType: "reasoning",
nextThoughtNeeded: true,
thoughtNumber: N,
totalThoughts: 30
});
}
2b: Search
Use the best available tool for the current sub-question:
- Exa / WebSearch: external knowledge, recent publications, API docs
- Grep / Glob / Read: codebase evidence, local files, prior research
- Knowledge graph:
tb.knowledge.searchEntities()for prior Thoughtbox findings
2c: Integrate
Record findings as a reasoning thought with evidence references. Include source URLs or file paths.
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.
- 8d ago First seen · 199 lines · 51 tokens per session scan A 2070b9ad1fed
thoughtbox:research is a skill published in the GitHub repository Kastalien-Research/thoughtbox (64 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,417 once invoked, about $0.0003 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
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
unity-yaml-editing
Last-resort guidance for safely hand-editing Unity YAML.
Threat Hunting & IOC Analysis
IOC extraction, threat intelligence correlation, MITRE ATT&CK mapping, hunt hypothesis generation, and detection rule creation.