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 ntorga/agent-starter-kit --skill web-searchgit clone --depth 1 https://github.com/ntorga/agent-starter-kitWrote 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/ntorga/agent-starter-kit/web-search)<a href="https://agentmods.dev/skills/ntorga/agent-starter-kit/web-search"><img src="https://agentmods.dev/badge/skills/ntorga/agent-starter-kit/web-search/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/ntorga/agent-starter-kit/web-search"><img src="https://agentmods.dev/badge/skills/ntorga/agent-starter-kit/web-search.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00913 |
| Opus 5 | $0.00007 | $0.00456 |
| Sonnet 5 | $0.00003 | $0.00183 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
web-search 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Answers about current facts, public tools, and external systems need web grounding. Search finds pages. Fetch reads them. Search runs through the TinyFish CLI. Page fetch tries the host's native web fetch tool first and falls back to the TinyFish CLI when the native tool is blocked. This skill defines when to use each surface, the exact commands, and how to read the output. Full flag reference: https://docs.tinyfish.ai/cli/commands
Procedure
Verify the tool is installed
-
Check for the CLI. Run
command -v tinyfish. If it is missing, stop and tell the user:- The TinyFish CLI is required for web search and fetch.
- Install it by following https://docs.tinyfish.ai/cli/commands.
- It is free, but it requires an API key — the user creates one and completes login with
tinyfish auth loginthemselves. Do not install the tool or runtinyfish auth loginon your own. Once the user confirms setup, continue.
-
Check authentication. Run
tinyfish auth status. If it reports no valid key, tell the user to runtinyfish auth loginthemselves and stop. Do not runtinyfish auth loginortinyfish auth seton your own.
Choose the surface
- Answer from local context first. Use project files and the conversation when they hold the answer. Skip the web when the question is about this codebase.
- Search when the right page is unknown. Use search for "what is", "how does", and "compare" questions, and for anything time-sensitive: versions, releases, prices, news.
- Fetch when the page is known. Try the host's native web fetch tool first. Fall back to
tinyfish fetch content getwhen the native tool is blocked, fails, or returns empty content.
Search
-
Run the search:
tinyfish search query "best React state management libraries"Add hints when the question is geo- or language-specific:
tinyfish search query "best pho in Saigon" --location "Vietnam" --language "en"
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 · 72 lines · 14 tokens per session scan A 5fa603e0a153
web-search is a skill published in the GitHub repository ntorga/agent-starter-kit (142 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 913 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-09-13.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
verify-samples-tool
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.