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 agents/metedata/remarc/webhooksgit clone --depth 1 https://github.com/metedata/RemarcWhat 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.00033 | $0.00886 |
| Opus 5 | $0.00016 | $0.00443 |
| Sonnet 5 | $0.00007 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webhooks are the handoff path for tools that do not speak MCP: Remarc sends comment events to any URL as an HTTP POST with a JSON body. That covers Zapier, Make, n8n, IFTTT, Slack incoming webhooks, and anything else that accepts JSON. Configure them in the Webhooks tab in Settings.
Add a webhook
Click Add Webhook to open the editor:
- Name: identifies the webhook in the list and when sending a card manually.
- URL: must be a valid http or https URL.
- Events: check which events this webhook receives. All are on by default.
- Signing secret (optional): when set, requests include a
webhook-signatureheader (HMAC SHA-256, Standard Webhooks format).whsec_secrets are supported. - Custom payload template (optional): replace the default JSON body with your own, for example for Slack incoming webhooks.
Each webhook in the list has a test button (paperplane), edit and delete buttons, and an enable switch. After a delivery, a status icon appears next to the name; hover it for the delivery time and, on failure, the error.
Events
Subscribable events and when each fires:
| Event | Fires when |
|---|---|
comment.created |
A comment is created |
comment.updated |
A comment's text or attachments change, or it moves to another session |
comment.status_changed |
A comment's status changes to anything other than resolved |
comment.resolved |
A comment is resolved |
comment.deleted |
A comment is deleted |
comment.sent |
You send a card manually (see below) |
webhook.test |
You click the test button |
comment.sent and webhook.test ignore the event checkboxes; subscriptions only filter the automatic events.
Send a card manually
Every comment card has a paperplane action. Click it, pick one of your enabled webhooks, and Remarc delivers the comment immediately as a comment.sent event. A toast confirms the send.
Delivery
Remarc sends requests with Content-Type: application/json plus webhook-id and webhook-timestamp headers, and retries failed deliveries twice (after 2 and 10 seconds) with the same webhook-id so receivers can deduplicate. Any 2xx response counts as delivered; otherwise Remarc shows a failure toast and records the error on the webhook row.
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 · 72 lines · 33 tokens per session scan A 957531d7b099
webhooks is an agent published in the GitHub repository metedata/Remarc (66 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 886 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 agents, from other repositories
swift-mcp-expert
Expert assistance for building MCP servers in Swift with the FastMCP library. Use proactively when authoring @Tool / @MCPResource / @MCPPrompt types, configuring the FastMCP builder, defining @Generable schemas, or debugging FastMCP server issues.
tooling-runner
Haiku runner for TMDb build/test commands — executes exactly one make target (or its xcode-tools MCP equivalent), writes the full output to a .build/last-.log file, and returns only a concise pass/fail + failures-as-file:line summary. Spawned by the /build, /build-for-testing, /test, and /integration-test skills; not…
task-agents
The primary agent workflow — inference setup resolution, the automation switch, evidence-first execution, tool policy, and the proposal/confirmation loop.
Native SwiftUI Builder
Builds complex custom SwiftUI views using standard SwiftUI components with TTBaseUIKit design tokens (XView/XSize/XFont). Does NOT use TTBaseSUI wrapper components.
kmp-architect
KMP architecture expert. Designs shared module structures, expect/actual patterns, navigation, and DI for Kotlin Multiplatform projects.
ios-reviewer
Expert iOS code reviewer. Reviews Swift code for quality, SwiftUI patterns, Combine/concurrency usage, and Apple best practices. Use PROACTIVELY after writing iOS code. MUST BE USED for all iOS changes.