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 commands/webhook-co/webhook/feature-devgit 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.00000 | $0.00757 |
| Opus 5 | $0.00000 | $0.00378 |
| Sonnet 5 | $0.00000 | $0.00151 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
feature-dev 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/feature-dev
Take a feature from a rough idea to reviewed, tested implementation through explicit phases. Don't jump straight to code — move through the phases in order and check in at the gates.
Phase 1 — discovery
Restate the goal in one line: who it's for, which surface(s) (CLI / API / web / MCP), and the outcome
they want. If the ask is vague, run the brainstorming skill / /brainstorming first and come back
with an agreed brief.
Phase 2 — codebase exploration
Understand before changing. Find where this lives: the relevant apps/* and packages/*, the
shared/ types, existing patterns for the same capability on other surfaces, and the tests that
cover the area. Note constraints discovered (DO ownership, RLS, the container-delivery seam). Use the
Explore subagent for broad searches when useful.
Phase 3 — clarifying questions
Before designing, ask the questions whose answers would change the design — auth/tenant context, data sensitivity (PII/PHI, raw payloads in R2), parity scope, ordering/performance needs, and which non-negotiables apply. Ask rather than assume. Wait for answers on anything load-bearing.
Phase 4 — architecture design (multiple approaches)
Present two or three viable approaches with concrete tradeoffs (complexity, parity cost,
performance, blast radius, how cleanly each respects the non-negotiables). Recommend one and say why
— have a point of view. Get agreement before implementing. Design for parity from the start: a
capability added to one surface is considered for all four, with shared shared/ types.
Phase 5 — implementation
Implement the agreed approach under TDD (failing test first → minimum code → refactor; see the
test-driven-development skill). Workers handlers stay thin (validate → delegate → respond); retries
via DO Alarms; delivery idempotent and dedup-by-event-id; Standard-Webhooks-native signing only;
open-core code must not import from ee/. For new MCP surface work, use the build-mcp-server skill.
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 · 60 lines · 0 tokens per session scan A 64919c500871
feature-dev is a command published in the GitHub repository webhook-co/webhook (0 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 757 tokens. 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 commands, from other repositories
sonicjs-pr-fixer
You are a specialized agent that helps fix and merge problematic PRs in the SonicJS repository. This includes PRs from forks that need cherry-picking, Dependabot PRs that need e2e tests enabled, and any PR that needs fixes before merging.
sonicjs-seo
You are an SEO expert agent for SonicJS, a modern headless CMS built for Cloudflare's edge platform. Your goal is to help SonicJS rank for relevant keywords and grow organic traffic through legitimate, high-quality content strategies.
hyperliquid-risk
Mission-critical real-time risk monitoring system with automated alerts, circuit breakers, and emergency shutdown for live Hyperliquid trading by ae.ltd.
migrate
Apply pending D1 migrations to local (default) or remote.
init
Scaffold the project files I like — CLAUDE.md and the /docs skeleton.
design
Interview the solution — architecture, schema, platform. Owns ARCHITECTURE.md + SPEC.md.