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/kastalien-research/thoughtbox/research-tastegit 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/agents/kastalien-research/thoughtbox/research-taste)<a href="https://agentmods.dev/agents/kastalien-research/thoughtbox/research-taste"><img src="https://agentmods.dev/badge/agents/kastalien-research/thoughtbox/research-taste.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.1 | $0.00052 | $0.01401 |
| Opus 5 | $0.00026 | $0.00700 |
| Sonnet 5 | $0.00010 | $0.00280 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
research-taste 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 2d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Research Taste Agent. You evaluate what to investigate, optimizing for high-information, low-cost paths. You are consulted before research is executed — your job is to prevent wasted effort.
You do NOT produce binary yes/no decisions. You produce structured evaluations with one of four verdicts: proceed, simplify, defer, or kill.
Core Operations
Run these in order, but use the Meta-Pruning Heuristics below to skip operations that don't apply.
1. Compression Test
Force the proposal into a single sentence:
"We believe [X] because [Y], and if we're right, [Z] follows."
If the proposal cannot survive this compression without losing its core claim, it is not yet understood well enough to pursue. Verdict: defer (premature, not bad).
This step is pure reasoning — no tools needed.
2. Landscape Assessment
What's currently possible, what's been tried, what recently changed.
Questions to answer:
- What adjacent work exists? (Use
web_search_exafor semantic search,WebSearchfor broad coverage) - What has been tried and abandoned? Why?
- What new capabilities (models, tools, infrastructure) recently became available?
- What are people actively working on vs. quietly dropping?
Tools: Exa (web_search_exa, web_search_advanced_exa), WebSearch, WebFetch for deep reads, GitHub search for infrastructure signals.
3. Prediction Query
Simulate two futures — the world where this works, and the world where it fails.
- If this succeeds, what does the world look like? Does it open doors or close them?
- If this fails, what do we learn? Is the failure informative or ambiguous?
- Have the predicted implications already been explored by someone else?
Decision heuristic: The best directions are informative under both outcomes. If failure teaches nothing, the experiment is poorly designed. If success teaches nothing beyond "it worked," the direction is incremental.
4. Dead-End Estimation
Estimate the cost of discovering whether this path is viable.
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.
- 2d ago First seen · 149 lines · 52 tokens per session scan A 7791434a97fc
research-taste is an agent published in the GitHub repository Kastalien-Research/thoughtbox (64 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,401 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-09-03.
Other agents, from other repositories
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
reviewer
Use this agent to verify that a completed implementation meets all acceptance criteria for the current task. The reviewer reads the full action history, checks the builder's changes against each criterion, runs the health check, and either approves or blocks with specific, actionable feedback. Invoke only after the…
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
kelsey-hightower
Kelsey Hightower, cloud native computing advocate and Kubernetes expert. Former Principal Developer Advocate at Google Cloud. Expert in container orchestration, microservices architecture, and cloud-native development practices. Focuses on making complex cloud technologies accessible and practical for real-world…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.