TinyFish Cookbook is a collection of example applications, recipes, and automations built with TinyFish, a web service that lets AI agents search the live web, read pages, and perform browser-based tasks. Developers use it to learn how to build web agents and connect them with workflows such as research, monitoring, and data collection. The catalogue entries provide agent skills and integrations for working with these examples and TinyFish endpoints.
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/tinyfish-io/tinyfish-cookbook/dev-pain-findernpx skills add tinyfish-io/tinyfish-cookbook --skill dev-pain-findergit clone --depth 1 https://github.com/tinyfish-io/tinyfish-cookbookWrote 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/tinyfish-io/tinyfish-cookbook/dev-pain-finder)<a href="https://agentmods.dev/skills/tinyfish-io/tinyfish-cookbook/dev-pain-finder"><img src="https://agentmods.dev/badge/skills/tinyfish-io/tinyfish-cookbook/dev-pain-finder.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.00160 | $0.02615 |
| Opus 5 | $0.00080 | $0.01307 |
| Sonnet 5 | $0.00032 | $0.00523 |
| Haiku 4.5 | $0.00016 | $0.00262 |
Grade A, and why
dev-pain-finder 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 6d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Pain Finder
Given a keyword or problem space, scrape real developer complaints from Reddit, Hacker News, dev.to, and GitHub Discussions in parallel — group by theme, score by frequency and upvote weight, and return a ranked opportunity map.
Pre-flight check
tinyfish --version
tinyfish auth status
If not installed: npm install -g tinyfish
If not authenticated: tinyfish auth login
Step 1 — Clarify input
You need:
- Keyword or problem space — e.g. "authentication", "deployment pipelines", "ORM", "Kubernetes", "state management"
If the user hasn't provided one, ask before proceeding. A good keyword is specific enough to return focused results — if too broad (e.g. "JavaScript"), ask them to narrow it down.
Step 2 — Parallel scraping
Fire all 5 agents simultaneously. Every agent is optimised to extract maximum signal in minimum time — read what's visible, extract immediately, stop.
# ── AGENT 1 — Reddit (stealth, search results only) ──────────
tinyfish agent run \
--url "https://www.reddit.com/search/?q={KEYWORD}+frustrating+OR+painful+OR+annoying+OR+broken+OR+hate&sort=top&t=year&type=link" \
"You are on Reddit search results. Your only job is to extract pain points fast.
Read the post titles and score/comment counts visible on this page. Nothing else.
Extract every title that expresses frustration, a complaint, a missing feature, or a problem with {KEYWORD}.
For each one note: the title text, upvote score (if visible), and subreddit.
STRICT RULES — these are non-negotiable:
- Do NOT click any post. Ever. Read titles and snippets only.
- Do NOT scroll. Read only what loads on first render.
- Do NOT navigate anywhere. Stay on this exact page.
- Ignore posts that are not complaints or pain points.
- Stop after reading 20 results maximum.
Return JSON array: [{title, score, subreddit, snippet}]" \
--sync --browser-profile stealth > /tmp/dpf_reddit.json &
# ── AGENT 2 — Reddit r/ExperiencedDevs + topic subreddits ────
tinyfish agent run \
--url "https://www.reddit.com/search/?q={KEYWORD}&restrict_sr=0&sort=top&t=year&type=link&subreddit=webdev+programming+devops+ExperiencedDevs+softwaredevelopment" \
"You are on Reddit search results filtered to developer subreddits. Extract pain points fast.
Read only post titles and visible snippets. Do not interact with the page.
Extract titles expressing: bugs, missing features, poor DX, complexity complaints, tool failures, workflow friction about {KEYWORD}.
For each: title text, subreddit, upvote score if visible.
STRICT RULES:
- Do NOT click anything
- Do NOT scroll
- Read exactly what is on screen, then stop
- Maximum 20 results
Return JSON array: [{title, score, subreddit, snippet}]" \
--sync --browser-profile stealth > /tmp/dpf_reddit2.json &
# ── AGENT 3 — Hacker News ─────────────────────────────────────
tinyfish agent run \
--url "https://hn.algolia.com/?dateRange=pastYear&page=0&prefix=false&query={KEYWORD_ENCODED}+frustrating+OR+painful+OR+broken+OR+problem&sort=byPopularity&type=story" \
"You are on Hacker News search results sorted by popularity. Extract pain points fast.
Read the story titles, point scores, and comment counts visible on this page.
Extract every story title that describes a problem, frustration, complaint, or missing capability related to {KEYWORD}.
For each: title text, points, comment count.
STRICT RULES:
- Do NOT click any story link
- Do NOT paginate
- Do NOT scroll past the first visible set of results
- Read only titles and metadata shown in the listing
- Maximum 15 results
- Stop immediately after extracting — do not explore further
Return JSON array: [{title, points, comments}]" \
--sync > /tmp/dpf_hn.json &
# ── AGENT 4 — dev.to ──────────────────────────────────────────
tinyfish agent run \
--url "https://dev.to/search?q={KEYWORD_ENCODED}+problem+OR+frustration+OR+painful+OR+hate+OR+annoying" \
"You are on dev.to search results. Extract developer pain points fast.
Read only the article titles, reaction counts, and tag labels visible in the search listing.
Extract articles whose titles describe a problem, complaint, frustration, or missing solution related to {KEYWORD}.
For each: title, reaction count if visible, tags.
STRICT RULES:
- Do NOT click any article
- Do NOT scroll more than once
- Do NOT navigate away
- Read only what is visible in the search result cards
- Maximum 15 results then stop immediately
Return JSON array: [{title, reactions, tags}]" \
--sync > /tmp/dpf_devto.json &
# ── AGENT 5 — GitHub Discussions ──────────────────────────────
tinyfish agent run \
--url "https://github.com/search?q={KEYWORD_ENCODED}+pain+OR+frustrating+OR+broken+OR+missing+OR+annoying&type=discussions&s=reactions&o=desc" \
"You are on GitHub Discussions search results sorted by most reactions. Extract pain points fast.
Read only the discussion titles, reaction counts, and repository names visible in the listing.
Extract discussions that describe a real problem, missing feature, DX complaint, or frustration with {KEYWORD}.
For each: title, reaction count, repo name.
STRICT RULES:
- Do NOT click any discussion link
- Do NOT paginate
- Do NOT scroll
- Read only what is visible on first load
- Maximum 15 results then stop
Return JSON array: [{title, reactions, repo}]" \
--sync > /tmp/dpf_github.json &
# ── WAIT ──────────────────────────────────────────────────────
wait
echo "=== REDDIT 1 ===" && cat /tmp/dpf_reddit.json
echo "=== REDDIT 2 ===" && cat /tmp/dpf_reddit2.json
echo "=== HN ===" && cat /tmp/dpf_hn.json
echo "=== DEVTO ===" && cat /tmp/dpf_devto.json
echo "=== GITHUB ===" && cat /tmp/dpf_github.json
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 240 lines · 160 tokens per session scan A d6cbdcb04644
dev-pain-finder is a skill published in the GitHub repository tinyfish-io/tinyfish-cookbook (2,153 stars, last pushed 5d ago), licensed MIT. It adds 160 tokens to every session and 2,615 once invoked, about $0.0008 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
11-browser-qa
Run post-review browser QA and produce short named videos for a locked happy path and sourced browser edge cases. Use when the user wants concise reviewer evidence for a web journey. Not for API, CLI, automated tests, diff review, or application fixes.
browser
Browser automation via the agent-browser CLI. Use when the user needs to drive websites or Electron desktop apps — navigating, filling forms, clicking, screenshots, extracting data, testing web apps, visual UI checks, the Pi Dashboard's Electron shell, or the user's own logged-in browser (SSO/2FA sites). Triggers…
06-test
Write and iterate tests until they pass, or validate a user journey end to end in the browser. Use when the user wants to add coverage, find what's untested, or walk a flow. Not for auditing test health or debugging a failure.
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
web-game-development
Implement and optimize browser games using Phaser, Three.js, React Three Fiber, Babylon.js, or PlayCanvas with responsive input, asset loading, rendering, and browser playtests. Use for JavaScript or TypeScript game projects.
browser-qa
Validate web applications through the embedded browser with responsive, interaction, console, and screenshot checks.