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/jsegov/shipspec-claude-code-plugin/researchnpx skills add jsegov/shipspec-claude-code-plugin --skill researchgit clone --depth 1 https://github.com/jsegov/shipspec-claude-code-pluginWhat 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.00057 | $0.01257 |
| Opus 5 | $0.00028 | $0.00629 |
| Sonnet 5 | $0.00011 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Skill
Guide WebSearch usage to find authoritative technology documentation and best practices.
When to Use
Invoke research when encountering:
- Unknown API or framework features
- Implementation patterns for specific technology
- Version-specific documentation needs
- Best practices for technical decisions
- Integration requirements with external services
Search Query Formulation
Basic Pattern
Structure queries as:
[technology] [version] [specific topic] documentation [year]
Examples:
- "Next.js 14 app router data fetching documentation 2026"
- "PostgreSQL 16 JSON operators documentation"
- "Tailwind CSS v4 responsive design patterns"
- "React 19 server components patterns 2026"
Version-Specific Searches
Always include version numbers when relevant:
- Framework versions: "Next.js 14", "React 19", "Vue 3"
- Language versions: "Python 3.12", "TypeScript 5.x", "Node.js 22"
- Database versions: "PostgreSQL 16", "MongoDB 7"
Year-Aware Searches
Include current year (2026) for recent documentation:
- Ensures results reflect latest API changes
- Avoids outdated patterns and deprecated features
- Finds current best practices
Targeting Authoritative Sources
Official Documentation Domains
| Technology | Primary Domain | Notes |
|---|---|---|
| React | react.dev | Canonical React docs |
| Next.js | nextjs.org | App Router focus |
| TypeScript | typescriptlang.org | Type system reference |
| Node.js | nodejs.org | API documentation |
| Python | docs.python.org | Standard library |
| PostgreSQL | postgresql.org | SQL reference |
| Tailwind CSS | tailwindcss.com | Utility classes |
| Prisma | prisma.io | ORM documentation |
| Drizzle | orm.drizzle.team | ORM documentation |
Site-Restricted Searches
Use site restriction for targeted results:
[query] site:react.dev
[query] site:github.com/[org]
Examples:
- "server components patterns site:react.dev"
- "authentication middleware site:nextjs.org"
- "drizzle postgres setup site:orm.drizzle.team"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 210 lines · 57 tokens per session scan A 881bc51d66d9
research is a skill published in the GitHub repository jsegov/shipspec-claude-code-plugin (20 stars, last pushed 7mo ago), licensed MIT. It adds 57 tokens to every session and 1,257 once invoked, about $0.0003 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
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.
api-design
Design or review an HTTP/REST/GraphQL API for versioning, pagination, error shapes, idempotency, auth, status codes, cache headers, and breaking-change management. Use when asked to "design an API", "shape the endpoints", "design the schema", "add a new endpoint", "review this API", or when building/modifying a public…
create-mcp-server
Build, iterate, and evaluate Model Context Protocol (MCP) servers that expose external services as tools an LLM can call. Covers schema/tool design, error handling, pagination, MCP Inspector testing, and an eval set. Use when asked to "build an MCP server", "create an MCP tool", "wrap this API as MCP", "expose X to…
dependency-upgrade
Plan, batch, and verify dependency upgrades safely. Triages outdated packages into risk tiers, upgrades in order (dev/minor/patch first, runtime majors last), verifies each batch, and produces an auditable commit sequence. Use when asked to "upgrade deps", "bump packages", "update nodemodules", "fix vulnerabilities"…