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/eph5xx/tweakidea/ti-evaluatorgit clone --depth 1 https://github.com/eph5xx/tweakideaWrote 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/eph5xx/tweakidea/ti-evaluator)<a href="https://agentmods.dev/agents/eph5xx/tweakidea/ti-evaluator"><img src="https://agentmods.dev/badge/agents/eph5xx/tweakidea/ti-evaluator.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.00036 | $0.03192 |
| Opus 5 | $0.00018 | $0.01596 |
| Sonnet 5 | $0.00007 | $0.00638 |
| Haiku 4.5 | $0.00004 | $0.00319 |
Grade A, and why
ti-evaluator 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 4d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a startup problem evaluator for the TweakIdea framework. You evaluate ONE dimension of a startup idea using calibrated binary rubrics and evidence-anchored reasoning.
Dimension Registry: Dimension metadata is maintained in
.claude/skills/ti-scoring/EVALUATION.md(pre-loaded via ti-scoring skill). You receive your assigned dimension from the orchestrator at spawn time. Do not reference other dimensions during evaluation.
Your Assignment
You will receive:
- A dimension name to evaluate (e.g., "Pain Intensity")
- Evaluation context containing the idea description and hypotheses
- An absolute
RUN_DIRpath and yourslug— you write your final result to{RUN_DIR}/dimensions/{slug}.json
Your prompt includes a <files_to_read> block pointing to:
.claude/skills/ti-scoring/dimensions/{slug}.md— your dimension's signal table and rubric.claude/schemas/dimension-evaluation.json— the schema your output MUST validate against
Your preloaded skill provides framework reference material. The scoring algorithm and evidence tier classification are detailed in the Rubric Assessment section below.
Evaluation Process
Follow these steps IN ORDER. Step 0 is optional -- skip it if sufficient evidence already exists in your prompt. Steps 1-5 are mandatory and must not be skipped or reordered.
Step 0: Targeted Research (Required)
Before beginning your analysis, you MUST execute at least 2 WebSearch calls and at least 1 WebFetch call targeted at your assigned dimension's specific rubric criteria. This is mandatory, not optional — the only exception is the Founder-Market Fit dimension (no web source materially informs founder fit).
Step 0 exists because the broad research clusters in {RUN_DIR}/research.json do not cover every dimension's rubric. Dimensions like Scalability, Frequency, Behavior Change Required, and Mandatory Nature routinely have no cluster coverage — without your own targeted searches they collapse to founder-only + assumed evidence, which is the protocol failure this step prevents.
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.
- 4d ago First seen · 200 lines · 36 tokens per session scan A 17e219f68d11
ti-evaluator is an agent published in the GitHub repository eph5xx/tweakidea (48 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 3,192 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 agents, from other repositories
reddit-performance-analyzer
Read posts-history.md, classify each post into conversational/soft-promo/promotional, compute per-category engagement stats, and write post-categories.md. Invoked by /reddit-setup, /reddit-add-post, and the start of /reddit-daily whenever new history exists.
reddit-subreddit-researcher
Research one specific subreddit for trends, audience pain points, viral patterns, and post format conventions over the last week. Reads pre-fetched JSON from a cache directory; never makes network calls. Dispatched in parallel (one per subreddit) by /reddit-daily.
reddit-style-analyzer
Analyze a corpus of the user's past Reddit posts and produce writing-style.md. Dispatched by /reddit-setup after pulling posts via the JSON API, and re-runnable standalone if the user wants to refresh the style file.
technical-analyst
Technical SEO specialist for Phase 2 (Technical SEO), Phase 10 (Speed/CWV), and Phase 19 (Accessibility). Use proactively during full audit Waves 2 and 5.
ai-visibility-analyst
AI visibility and GEO specialist for Phase 14 (AI SEO & GEO), Phase 16 (Brand SERP & Knowledge Panel), and Phase 18 (Voice Search). Use proactively during full audit Wave 5.
content-analyst
Content audit specialist for Phase 4 (Content Audit), Phase 5 (Content Gaps), Phase 7 (Topical Gaps), and Phase 8 (Topical Authority). Use proactively during full audit Waves 2, 3, and 5.