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/serphouse/agent-skills/searchnpx skills add SERPHouse/agent-skills --skill searchgit clone --depth 1 https://github.com/SERPHouse/agent-skillsWrote 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/serphouse/agent-skills/search)<a href="https://agentmods.dev/skills/serphouse/agent-skills/search"><img src="https://agentmods.dev/badge/skills/serphouse/agent-skills/search.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.00023 | $0.01717 |
| Opus 5 | $0.00012 | $0.00859 |
| Sonnet 5 | $0.00005 | $0.00343 |
| Haiku 4.5 | $0.00002 | $0.00172 |
Grade A, and why
serphouse-search scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **REST API** | `src/api/SKILL.md` | The user wants curl commands, raw HTTP requests, endpoint URLs, rate limits, webhooks | How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SERPHouse Search & Knowledge Retrieval Skill
This skill teaches an agent how to find any SERPHouse documentation detail using the three authoritative sources in this project. Always ground answers in these sources — never guess endpoints, parameters, or behavior.
The Three Authoritative Sources
| Source | File | Use When... |
|---|---|---|
| REST API | src/api/SKILL.md |
The user wants curl commands, raw HTTP requests, endpoint URLs, rate limits, webhooks |
| MCP Server | src/mcp/SKILL.md |
The user wants to connect an AI client (Claude, Cursor, etc.) to live SERP data via MCP tools |
| Node.js SDK | src/nodejs/SKILL.md |
The user is writing JavaScript/TypeScript code using @serphouse/serphouse-nodejs |
How to Search for Any Detail
Step 1: Determine which source to consult
- If the question is about HTTP endpoints, auth, curl, webhooks, or rate limits →
src/api/SKILL.md - If the question is about MCP client config, tool names, or server setup →
src/mcp/SKILL.md - If the question is about code examples, SDK setup, TypeScript types, or error handling →
src/nodejs/SKILL.md
Step 2: Search the source file
Use the grep tool on the relevant SKILL.md to find the specific detail:
grep -- "desired search term" src/<source>/SKILL.md
Example searches:
- "What endpoint for Google Images?" → grep
google-imageinsrc/api/SKILL.md - "How to set up MCP auth?" → grep
headersorauthinsrc/mcp/SKILL.md - "How do I catch errors in the SDK?" → grep
SERPHouseErrororcatchinsrc/nodejs/SKILL.md
Step 3: If the detail isn't found
If a search term yields no results in the SKILL.md file:
- Try alternative terms — e.g., if "account info" returns nothing, try "account_info" or "balance"
- Check the official docs at https://docs.serphouse.com for endpoint-specific parameter details (also referenced in
src/nodejs/SKILL.md:293) - State clearly that this detail is not in the project's knowledge base rather than fabricating it
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.
- 5d ago First seen · 98 lines · 23 tokens per session scan A 8106281ad6ab
serphouse-search is a skill published in the GitHub repository SERPHouse/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,717 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
clarify
Adaptive requirements clarification with auto-depth routing. Shallow (Q&A) for simple tasks, Deep (exploration + DRAFT + PLAN) for complex ones. Escalates automatically when ambiguity persists.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.