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/cloudshipai/station/web-researchnpx skills add cloudshipai/station --skill web-researchgit clone --depth 1 https://github.com/cloudshipai/stationWhat 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 | $0.00014 | $0.00342 |
| Opus 5 | $0.00007 | $0.00171 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
web-research 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 3d 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.
What it actually says
Web Research Skill
When to Use
- User asks you to research a topic
- You need to gather information from multiple sources
- Task requires fact-checking or verification
Workflow
1. Define Scope
Before searching, clarify:
- What specific questions need answering?
- What depth of coverage is needed?
- Are there preferred or authoritative sources?
2. Search Strategy
Execute searches in this order:
- Broad overview search
- Specific fact-finding searches
- Alternative viewpoint searches
3. Source Evaluation
For each source, assess:
- Authority (who wrote it?)
- Currency (when published?)
- Relevance (does it answer the question?)
4. Synthesis
Combine findings into a coherent summary with citations.
Examples
Example: Technology Research
User: "Research the latest developments in WebAssembly"
Step 1: Define scope
- Focus on recent developments
- Include browser support status
- Cover WASI developments
Step 2: Execute searches
- "WebAssembly developments 2026"
- "WASI preview 2 status"
- "WebAssembly component model"
Step 3: Evaluate sources
- Prefer official documentation
- Cross-reference with reputable tech blogs
Step 4: Synthesize findings
- Create summary with citations
- Note any conflicting information
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.
- 3d ago First seen · 68 lines · 14 tokens per session scan A 09842aeb682a
web-research is a skill published in the GitHub repository cloudshipai/station (429 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 342 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-08-30.
Other skills, from other repositories
cq
INVOKE WHEN: Starting any task — query first (cq catches blind spots your training data missed: stale versions, integration gotchas, undocumented quirks) You just resolved a non-obvious error, confusing error message, or surprising tool behavior — present a draft KU to the user and call propose if they approve…
use-modern-go
Apply modern Go syntax guidelines based on project's Go version. Use when writing or modifying Go code to ensure modern idioms are used instead of legacy patterns.
symbolpeek
Token-efficient code, JSON, and Markdown navigation; use before whole-file reads.
cli-to-go-migration
Reusable agent skill for migrating command-line interfaces from any programming language to Go.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with…