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 skills add tinyfish-io/tinyfish-cookbook --skill freelance-gig-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/freelance-gig-finder)<a href="https://agentmods.dev/skills/tinyfish-io/tinyfish-cookbook/freelance-gig-finder"><img src="https://agentmods.dev/badge/skills/tinyfish-io/tinyfish-cookbook/freelance-gig-finder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tinyfish-io/tinyfish-cookbook/freelance-gig-finder"><img src="https://agentmods.dev/badge/skills/tinyfish-io/tinyfish-cookbook/freelance-gig-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00098 | $0.02058 |
| Opus 5.5 | $0.00039 | $0.00823 |
| Sonnet 5.5 | $0.00020 | $0.00412 |
| Haiku 4.5 | $0.00010 | $0.00206 |
Grade A, and why
freelance-gig-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 1mo 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Freelance Gig Finder
Search Upwork, Contra, We Work Remotely, Freelancer, and Toptal simultaneously for fresh freelance and contract opportunities matching your skill set — filtered to recent postings so you're not looking at stale listings.
Pre-flight Check (REQUIRED)
Before making any TinyFish call, always run BOTH checks:
1. CLI installed?
which tinyfish && tinyfish --version || echo "TINYFISH_CLI_NOT_INSTALLED"
If not installed, stop and tell the user:
Install the TinyFish CLI:
npm install -g @tiny-fish/cli
2. Authenticated?
tinyfish auth status
If not authenticated, stop and tell the user:
You need a TinyFish API key. Get one at: https://agent.tinyfish.ai/api-keys
Then authenticate:
tinyfish auth login
Do NOT proceed until both checks pass.
Step 1 — Gather inputs
You need:
- Skill or role — e.g.
React developer,Python,UI/UX designer,copywriter,DevOps,mobile developer - Budget preference (optional) — e.g.
hourly,fixed price,$50+/hr - Recency (optional) — default to listings posted in the last 7 days
If skill is not provided, ask before proceeding.
Step 2 — Parallel search
Fire all agents simultaneously.
# Agent 1 — Upwork
tinyfish agent run \
--url "https://www.upwork.com/nx/search/jobs/?sort=recency&q={SKILL_ENCODED}" \
"You are on Upwork job search results for '{SKILL}', sorted by most recent.
Extract the first 8 visible job listings.
For each listing extract:
- title
- client description snippet (what they need)
- budget (hourly rate range or fixed price if shown)
- posted time (e.g. '2 hours ago', 'yesterday')
- required skills listed
- job type (hourly/fixed)
- direct URL to the listing
STRICT RULES:
- Do NOT click any listing
- Read only what is visible in the search result cards
- Only include listings posted within the last 7 days
- Maximum 8 listings then stop
Return JSON array: [{title, description, budget, posted, skills: [], job_type, url}]" \
--sync > /tmp/fg_upwork.json &
# Agent 2 — Contra
tinyfish agent run \
--url "https://contra.com/opportunities?query={SKILL_ENCODED}&sort=recent" \
"You are on Contra job listings for '{SKILL}', sorted by newest.
Extract the first 8 visible job listings.
For each listing extract:
- title
- client/company name
- description snippet
- budget or rate (if shown)
- posted time
- required skills
- direct URL
STRICT RULES:
- Do NOT click any listing
- Read only what is visible in the listing cards
- Maximum 8 listings then stop
- If no results found, return {found: false}
Return JSON array: [{title, client, description, budget, posted, skills: [], url}]" \
--sync > /tmp/fg_contra.json &
# Agent 3 — We Work Remotely
tinyfish agent run \
--url "https://weworkremotely.com/remote-jobs/search?term={SKILL_ENCODED}" \
"You are on We Work Remotely job search results for '{SKILL}'.
Extract the first 8 visible job listings.
For each listing extract:
- title
- company name
- category (e.g. Front-End, Back-End, Design, etc.)
- posted date
- direct URL to the listing
STRICT RULES:
- Do NOT click any listing
- Read only what is visible in the search results
- Maximum 8 listings then stop
- If no results, return {found: false}
Return JSON array: [{title, company, category, posted, url}]" \
--sync > /tmp/fg_wwr.json &
# Agent 4 — Freelancer.com
tinyfish agent run \
--url "https://www.freelancer.com/jobs/?keyword={SKILL_ENCODED}" \
"You are on Freelancer.com job listings for '{SKILL}'.
Extract the first 8 visible job listings.
For each listing extract:
- title
- budget range (fixed or hourly)
- number of bids (if shown)
- posted time
- required skills listed
- direct URL
STRICT RULES:
- Do NOT click any listing
- Read only what is visible in the listing cards
- Maximum 8 listings then stop
Return JSON array: [{title, budget, bids, posted, skills: [], url}]" \
--sync > /tmp/fg_freelancer.json &
# Agent 5 — LinkedIn (contract/freelance filter)
tinyfish agent run \
--url "https://www.linkedin.com/jobs/search/?keywords={SKILL_ENCODED}&f_JT=C%2CF&f_WT=2&sortBy=DD" \
"You are on LinkedIn job search results for '{SKILL}' filtered to Contract and Freelance jobs, remote, sorted by most recent.
Extract the first 8 visible job listings.
For each listing extract:
- title
- company name
- location or remote status
- posted time
- salary or rate if shown
- direct URL
STRICT RULES:
- Do NOT click any listing
- Read only what is visible in the job cards
- Maximum 8 listings then stop
Return JSON array: [{title, company, location, posted, salary, url}]" \
--sync > /tmp/fg_linkedin.json &
wait
echo "=== UPWORK ===" && cat /tmp/fg_upwork.json
echo "=== CONTRA ===" && cat /tmp/fg_contra.json
echo "=== WWR ===" && cat /tmp/fg_wwr.json
echo "=== FREELANCER ===" && cat /tmp/fg_freelancer.json
echo "=== LINKEDIN ===" && cat /tmp/fg_linkedin.json
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.
- 1mo ago First seen · 225 lines · 98 tokens per session scan A d09c44a4026c
freelance-gig-finder is a skill published in the GitHub repository tinyfish-io/tinyfish-cookbook (2,274 stars, last pushed 5d ago), licensed MIT. It adds 98 tokens to every session and 2,058 once invoked, about $0.0004 per session on Opus 5.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
typescript-strict
TypeScript strict mode patterns with interfaces, type guards, generics, and utility types. Use when defining types, creating type-safe functions, handling nullable values, or implementing generic components.
agentscope-java
Expert Java developer skill for AgentScope Java framework - a reactive, message-driven multi-agent system built on Project Reactor. Use when working with reactive programming, LLM integration, agent orchestration, multi-agent systems, or when the user mentions AgentScope, ReActAgent, Mono/Flux, Project Reactor, or…
chat-sdk
Build multi-platform chat bots with Chat SDK (chat npm package). Use when developers want to (1) Build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, (2) Use Chat SDK to handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI…
type-safety
TypeScript type safety conventions for the Playwright scaffold — the "no any" rule, Zod 4 schema patterns (z.strictObject, top-level validators like z.uuid / z.email / z.url / z.int / z.enum), schemas built directly from the documented OpenAPI / Swagger contract (response envelope spelled out per endpoint), type…
enums
TypeScript enum conventions for the Playwright scaffold — PascalCase enum names, SCREAMINGSNAKECASE members, location rules for app-specific (enums/{area}/) vs shared/utility (enums/util/) constants, and the rules for adding or extending enums. Use when adding a new API endpoint path, UI message, role, storage-state…
refactor-values
Safe refactoring workflow for enum values, enum keys, and static test data in test-data/static/.ts — mandatory impact analysis, cascading updates, and verification. Use BEFORE changing any enum member's string value (ApiEndpoints., Messages., Roles, StorageStatePaths), renaming any enum key, or editing any existing…