Agentic Tools is a marketplace of plugins and skills for managing Meta Social Technologies applications, including settings, webhooks, compliance, app review, and API health. Developers use it with coding agents such as Claude Code, Cursor, and Codex through Meta's remote MCP server. The catalogue contains the project's agent add-ons.
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 facebook/agentic-tools --skill debug-webhooksgit clone --depth 1 https://github.com/facebook/agentic-toolsWrote 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/facebook/agentic-tools/debug-webhooks)<a href="https://agentmods.dev/skills/facebook/agentic-tools/debug-webhooks"><img src="https://agentmods.dev/badge/skills/facebook/agentic-tools/debug-webhooks/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/facebook/agentic-tools/debug-webhooks"><img src="https://agentmods.dev/badge/skills/facebook/agentic-tools/debug-webhooks.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.00040 | $0.01027 |
| Opus 5.5 | $0.00016 | $0.00411 |
| Sonnet 5.5 | $0.00008 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
debug-webhooks 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Webhooks
Diagnose and fix webhook delivery issues for a Meta app.
Workflow
-
Start tracking. Before any other work, call
devtools_skill_invocationwith actionstartandskill_namedebug-webhooks. Passskill_namedebug-webhookson everydevtools_*tool call in the following steps. -
Get context. Ask the user for:
- The app name or ID — if they give a name (or aren't sure of the ID), resolve it to an
app_idviadevtools_app_list(actionlist); if several apps match or it's ambiguous, show the candidates (name, ID, viewer role) and ask the user to pick - What's going wrong (not receiving events? wrong data? specific topic?)
- The app name or ID — if they give a name (or aren't sure of the ID), resolve it to an
-
Inspect current state. Run in parallel:
devtools_webhook_listwith actionlist_subscriptions— all active subscriptionsdevtools_webhook_listwith actionlist_topics— all available topics (for comparison)
-
Diagnose. Check for common issues:
No subscriptions found
- The topic the user expects events from has no active subscription
- Suggest using
/webhook-setupto create one
Subscription exists but no events received
- Send a test payload:
devtools_webhook_testwith actiontest_sendfor the relevant topic and field - If test fails: callback URL may be down, unreachable, or not returning 200
- If test succeeds but real events don't arrive: the issue is likely on the app side (permissions, page subscriptions, etc.)
Wrong fields subscribed
- Compare subscribed fields against what the user expects to receive
- If fields are missing: use
devtools_webhook_managewith actionupdate_fields, passing the missing fields viaadd_fields - If extra fields cause noise: use
devtools_webhook_managewith actionupdate_fields, passing unwanted fields viaremove_fields
Multiple subscriptions on same topic
- Flag potential conflicts or duplicate delivery
-
Test delivery. For each relevant subscription:
- Call
devtools_webhook_testwith actiontest_send - Report whether the test payload was accepted by the callback endpoint
- Call
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 · 84 lines · 40 tokens per session scan A fd36100093b0
debug-webhooks is a skill published in the GitHub repository facebook/agentic-tools (15 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 1,027 once invoked, about $0.0002 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
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
axiom-networking
Use when implementing or debugging ANY network connection, API call, or socket in an Apple app. Covers URLSession, Network.framework, NetworkConnection, connection diagnostics.