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/nirholas/xactions/webhooksnpx skills add nirholas/XActions --skill webhooksgit clone --depth 1 https://github.com/nirholas/XActionsWhat 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.00044 | $0.00599 |
| Opus 5 | $0.00022 | $0.00300 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
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 2d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webhooks
API-powered webhook system for receiving real-time event notifications from XActions.
Entry Points
| Goal | Route | Method |
|---|---|---|
| Create a webhook | POST /api/webhooks |
REST API |
| List webhooks | GET /api/webhooks |
REST API |
| Update a webhook | PATCH /api/webhooks/:id |
REST API |
| Delete a webhook | DELETE /api/webhooks/:id |
REST API |
| Test a webhook | POST /api/webhooks/:id/test |
REST API |
API Usage
Create a webhook
POST /api/webhooks
Authorization: Bearer <token>
Content-Type: application/json
{
"url": "https://your-server.com/webhook",
"events": ["operation.complete", "follower.lost", "follower.gained"],
"secret": "your-signing-secret"
}
Test a webhook
POST /api/webhooks/:id/test
Authorization: Bearer <token>
Sends a test payload to the registered URL.
Supported Events
| Event | Triggered when |
|---|---|
operation.complete |
An automation job finishes successfully |
operation.failed |
An automation job fails |
follower.gained |
You gain a new follower |
follower.lost |
You lose a follower |
job.started |
A Bull queue job begins |
job.completed |
A Bull queue job completes |
Payload Verification
Webhooks are signed with HMAC-SHA256 using your secret:
const signature = req.headers['x-xactions-signature'];
const expected = crypto.createHmac('sha256', secret)
.update(JSON.stringify(req.body))
.digest('hex');
const isValid = crypto.timingSafeEqual(
Buffer.from(signature),
Buffer.from(expected)
);
Notes
- Webhook deliveries are retried up to 3 times on failure (exponential backoff)
- Delivery logs are available via
GET /api/webhooks/:id/deliveries - Events are dispatched asynchronously from the Bull job queue
Related Skills
- xactions-mcp-server — AI agent integration alternative to webhooks
- follower-monitoring — Source of
follower.gained/follower.lostevents - analytics-insights — Pull analytics instead of waiting for events
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.
- 2d ago First seen · 86 lines · 44 tokens per session scan A b7a122e71701
webhooks is a skill published in the GitHub repository nirholas/XActions (492 stars, last pushed 4d ago), licensed Apache-2.0. It adds 44 tokens to every session and 599 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-30.
Other skills, from other repositories
stripe-projects
Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.
tape-opens
Stack-unwind review of this conversation - a tree of main tasks done (struck through) and every open left behind at the depth it was abandoned, sized by the thread's measured shape, never by feel. Optional argument - a .jsonl path or session id to review a different session.
prompt-optimization
Improve a prompt on the evaluations workbench through a measured loop. Score the baseline first, then duplicate the target column, form a hypothesis from failing rows, edit the copy's prompt draft, run, compare pass rate and cost, and repeat until the numbers hold. Use when the user asks to optimize or improve a…
connect-agent
Connect the codebase's AI agent to LangWatch agent simulations over HTTP, so test suites run against it from the platform. Finds or adds the agent's chat endpoint, wires authentication for scenario traffic, makes the server adopt the W3C traceparent header so the judge reads the agent's own traces, registers the agent…
agent-improve
Turns production evidence into tested improvements for your AI agent. Forms hypotheses from real traces and analytics, explains the reasoning behind each one, then executes with the user: scenario tests that reproduce production failures, prompt and code changes as reviewable PRs, new evaluators and monitors that…
feature-map
Maintain the canonical LangWatch feature map (/feature-map.json). Use when adding features, APIs, MCP tools, CLI commands, or skills — to update the central registry and keep surfaces in sync.