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 SERPHouse/agent-skills --skill nodejsgit 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/nodejs)<a href="https://agentmods.dev/skills/serphouse/agent-skills/nodejs"><img src="https://agentmods.dev/badge/skills/serphouse/agent-skills/nodejs/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/serphouse/agent-skills/nodejs"><img src="https://agentmods.dev/badge/skills/serphouse/agent-skills/nodejs.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.00028 | $0.02479 |
| Opus 5.5 | $0.00011 | $0.00992 |
| Sonnet 5.5 | $0.00006 | $0.00496 |
| Haiku 4.5 | $0.00003 | $0.00248 |
Grade A, and why
serphouse-nodejs 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@serphouse/serphouse-nodejs SDK Skill
This skill equips the agent to use the official SERPHouse Node.js SDK (@serphouse/serphouse-nodejs) for live SERP data — Google, Bing, Yahoo search results plus Jobs, Local, Videos, Shopping, Autocomplete, and more.
When to Use
Trigger when the user's project uses (or should use) @serphouse/serphouse-nodejs and needs help with:
| Category | Example prompts |
|---|---|
| Setup | "Install serphouse-nodejs and set up the client" |
| Google SERP | "Search Google for 'best CRM' from the US on desktop" |
| Bing/Yahoo SERP | "Run a Bing news search for 'AI startups'" |
| Google Verticals | "Find software engineer jobs on Google Jobs in SF" or "Get autocomplete suggestions for 'best saas'" |
| Location | "Find the loc_id for Austin, Texas" |
| Account | "Check my SERPHouse credit balance" |
| Error handling | "Catch and log SERPHouse API errors" |
| TypeScript | "Import the correct types for a Google search" |
| HTML responses | "Get raw HTML instead of JSON" |
Do not trigger for general web scraping or non-SERPHouse APIs.
Installation
npm install @serphouse/serphouse-nodejs
Requires Node.js 18+ (uses fetch natively). No runtime dependencies.
Quick Start
import { SERPHouse } from '@serphouse/serphouse-nodejs';
const client = new SERPHouse('YOUR_API_KEY');
// Namespaced style
const { results } = await client.google.search({
q: 'Fresh Bagels',
domain: 'google.com',
lang: 'en',
device: 'desktop',
loc: 'New York,United States',
});
// Flat alias style (same result)
const { results } = await client.google_search({
q: 'Fresh Bagels',
domain: 'google.com',
lang: 'en',
device: 'desktop',
loc: 'New York,United States',
});
CommonJS is also supported:
const { SERPHouse } = require('@serphouse/serphouse-nodejs');
Client Options
const client = new SERPHouse('API_KEY', {
baseUrl: 'https://api.serphouse.com', // default
timeout: 60000, // default, ms
});
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 · 299 lines · 28 tokens per session scan A 23d0cfb8702d
serphouse-nodejs is a skill published in the GitHub repository SERPHouse/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 2,479 once invoked, about $0.0001 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-31.
Other skills, from other repositories
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
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.
setting-up-a-project
Use when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.
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.