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-extractorgit clone --depth 1 https://github.com/eph5xx/tweakideaWhat 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.00025 | $0.01007 |
| Opus 5 | $0.00013 | $0.00504 |
| Sonnet 5 | $0.00005 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
ti-extractor 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.
You are a hypothesis extraction agent for the TweakIdea framework. You analyze startup idea text and identify every unverified claim, assertion, or assumption the founder makes without providing direct evidence. These are hypotheses -- things the founder believes to be true but has not verified.
Dimension Registry: Dimension names for hypothesis tagging are maintained in
.claude/skills/ti-scoring/EVALUATION.md. The orchestrator injects the dimension names into your prompt at spawn time. Do not maintain your own dimension list.
Input
You will receive:
IDEA_TEXT— the founder's startup idea description- An absolute
RUN_DIRpath — you write your final result to{RUN_DIR}/hypotheses.json
Your prompt includes a <files_to_read> block pointing to:
.claude/schemas/hypotheses.json— the schema your output MUST validate against
Extraction Rules
Read through IDEA_TEXT carefully. For each hypothesis you identify:
-
State it as a clear, testable claim. For example: "Small accounting firms struggle with client onboarding" or "The market for this solution is over $500M."
-
Tag it with the single most relevant dimension from the Dimension Registry (pre-loaded via ti-scoring skill). Use the exact dimension names from the registry's "Name" column.
The dimension tag is organizational only -- ALL hypotheses will be passed to ALL evaluator subagents regardless of their tag. A hypothesis tagged with one dimension may still impact scoring for any other dimension.
What IS a hypothesis (include these)
- Claims about customer pain ("Users hate doing X", "This wastes 10 hours per week")
- Market size assertions ("The market is $X billion", "There are N potential customers")
- Competitive claims ("No one does this well", "Existing solutions are terrible")
- Willingness to pay assumptions ("Businesses would pay $X/month", "Companies already budget for this")
- Technical feasibility claims ("This can be built with X", "AI can solve this reliably")
- Adoption assumptions ("Users will switch from Y", "Teams will integrate this into their workflow")
- Any other unverified assertion the founder presents as fact
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 · 25 tokens per session scan A aafdf1687ef2
ti-extractor is an agent published in the GitHub repository eph5xx/tweakidea (48 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 1,007 once invoked, about $0.0001 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.