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 skills/kastalien-research/thoughtbox/evalnpx skills add Kastalien-Research/thoughtbox --skill evalgit clone --depth 1 https://github.com/Kastalien-Research/thoughtboxWhat 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.00035 | $0.00715 |
| Opus 5 | $0.00017 | $0.00358 |
| Sonnet 5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
eval 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evaluation harness: $ARGUMENTS
Commands
Parse the first word of $ARGUMENTS to determine the command:
metrics — Show current session metrics
Collect and display metrics for the current session:
- Count commits:
git log --oneline --since="today" | wc -l - Count test results: check for recent vitest output or
.eval/metrics/entries - Token usage: check LangSmith state file if available
- Pattern usage: check
.dgm/fitness.jsonfor patterns used this session - Session duration: check session start time from logs
Display as:
## Current Session Metrics
| Metric | Value | Baseline | Delta |
|--------|-------|----------|-------|
| Commits | 5 | 3.2 avg | +56% |
| Tests passing | 42/42 | 40/42 | +2 |
| Files changed | 12 | 8.5 avg | +41% |
| Patterns used | 7 | 5.3 avg | +32% |
baseline — Set or update baselines
- Read the last N session metric snapshots from
.eval/metrics/ - Calculate averages for each metric
- Write to
.eval/baselines.json - Report what changed
compare — Compare sessions
Usage: compare --last N or compare --session <id>
- Load metric snapshots from
.eval/metrics/ - Compare against baselines
- Highlight regressions (metric dropped >10% below baseline)
- Highlight improvements (metric improved >10% above baseline)
report — Generate weekly evaluation report
- Load all metrics from the past 7 days
- Calculate trends (improving, stable, declining)
- Identify top improvements and top regressions
- Generate recommendations based on trends
capture — Capture current session metrics
Write a metric snapshot to .eval/metrics/session-{timestamp}.json:
{
"session_id": "<session id>",
"timestamp": "<ISO 8601>",
"branch": "<git branch>",
"metrics": {
"commits": 0,
"tests_total": 0,
"tests_passing": 0,
"files_changed": 0,
"patterns_referenced": 0,
"assumptions_verified": 0,
"escalations": 0,
"spiral_detections": 0
},
"qualitative": {
"session_focus": "<what the session was about>",
"memory_usefulness": 0,
"knowledge_gaps_found": []
}
}
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 · 88 lines · 35 tokens per session scan A 5d85cc0bd238
eval is a skill published in the GitHub repository Kastalien-Research/thoughtbox (64 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 715 once invoked, about $0.0002 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
reasoning
Use BEFORE answering analytical, diagnostic, planning, or multi-step reasoning questions. Trigger phrases include "should I X or Y", "why is X happening", "what's the best approach", "what are the tradeoffs", "help me think through", "diagnose", "root cause", "plan/design X", "what are the implications of", "compare…
xcodebuildmcp-structured-output-review
Use when reviewing XcodeBuildMCP structured output schema changes, schema versioning, manifest outputSchema metadata, and JSON fixture compatibility.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
cortex-automate
Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…
tabnexus-mcp-evals
Generate, validate, and run isolated Codex-to-TabNexus MCP evaluations with a curated 600-query dataset, executable gold tool labels, safety checks, and best-of-three stability scoring. Use when testing TabNexus MCP tool coverage, Agent behavior, regression quality, destructive-action safety, prompt changes, or a…
compare
Structured comparison of 2+ alternatives with consistent criteria and decision matrix.