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/webhook-co/webhook/docs-and-api-referencenpx skills add webhook-co/webhook --skill docs-and-api-referencegit clone --depth 1 https://github.com/webhook-co/webhookWhat 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.00047 | $0.00417 |
| Opus 5 | $0.00023 | $0.00209 |
| Sonnet 5 | $0.00009 | $0.00083 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
docs-and-api-reference 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 yesterday.
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
Docs & API reference
Produce clear, on-voice developer documentation and keep every surface documented at parity.
Parity is the core job
A capability exists on CLI, API, web, and MCP identically — so it must be documented on all four. When you document a feature:
- Show it across each relevant surface (CLI command, API request, web flow, MCP tool).
- Use the same payload/types across surfaces (sourced from
shared/); don't invent per-surface shapes. - Cross-link the surfaces so a reader can switch between them.
Voice & style
- Follow the
writing-voicerule: precise, quietly opinionated, developer-to-developer, dry wit that never costs clarity. - Lowercase
webhook.co/wbhk.my; sentence case for headings and UI labels. - Lead with what the reader can do; runnable examples over prose. Every code sample should work.
Source of truth
- API reference is generated from the spec (SDKs via Speakeasy/Stainless) — keep prose docs in sync with the generated reference; don't hand-maintain endpoint tables that drift.
- Document Standard Webhooks signing/verification using the spec's terms (send and receive).
Guardrails
- This repo is public-safe: no prices, tiers, cost figures, margins, or business strategy in any doc. Describe pricing only qualitatively (transparent, predictable, soft-cap that pauses) if at all.
- Never include secrets, real tokens, or account IDs in examples — use clear placeholders.
Progressive disclosure
Keep this skill lean; put doc-site structure, frontmatter conventions, and per-surface example
templates in references/.
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.
- yesterday First seen · 43 lines · 47 tokens per session scan A 12a63b5dd204
docs-and-api-reference is a skill published in the GitHub repository webhook-co/webhook (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 47 tokens to every session and 417 once invoked, about $0.0002 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-31.
Other skills, from other repositories
update-saasmail
Sync the local saasmail repo with the latest upstream changes from https://github.com/choyiny/saasmail. Use this skill whenever the user wants to update saasmail, pull upstream changes, sync with upstream, rebase on upstream, get the latest saasmail, or says "/update-saasmail". Handles adding the upstream remote if…
story-html-publisher
Final step of the AI Storybook pipeline. Consolidates the scenes, images, and per-scene audio into ONE self-contained HTML storybook — a swipe/tap player with every image and audio clip embedded as base64 so the single file works offline and can be shared as-is. Reads {slug}scenes.json, {slug}images.json, and…
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
Pair Programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
Skill Builder
Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when you need to build custom skills for specific workflows, generate skill templates, or understand the Claude Skills specification.