track3-webhooks-idempotency

Name: track3-webhooks-idempotency
Author: joshrkay

Traces Stripe webhook handling and idempotency. A double-applied payment webhook is the canonical silent money bug — passes every test, surfaces as a reconciliation gap.

by joshrkay(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Claude Code subagent imported from joshrkay/Serviceos (.claude/agents/track3-webhooks-idempotency.md). Copyright stays with the author.

Find the Stripe webhook handler(s). Determine:

Idempotency mechanism: is there a dedupe on Stripe event ID? Is it enforced at the DB level (unique constraint) or in application code (racy)? What happens on redelivery of an already-processed event?
Signature verification: present, and does it fail closed?
Event coverage: are payment-intent, charge, and refund event types each handled, and can any of them double-apply?
Transaction boundary: are webhook processing and the balance/status update in one transaction, or can they partially commit?

Report file:line. Report EXISTS / PARTIAL / ABSENT per item. Do not propose fixes.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/joshrkay-serviceos-track3-webhooks-idempotency-subagent/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

joshrkay-serviceos-track3-webhooks-idempotency-subagent.ocm.jsonjson

{
  "ocm": "1",
  "id": "joshrkay-serviceos-track3-webhooks-idempotency-subagent",
  "kind": "agent",
  "name": "track3-webhooks-idempotency",
  "description": "Traces Stripe webhook handling and idempotency. A double-applied payment webhook is the canonical silent money bug — passes every test, surfaces as a reconciliation gap.",
  "publisher": "joshrkay",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "agent-md",
      "github-claude-agents"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Traces Stripe webhook handling and idempotency. A double-applied payment webhook is the canonical silent money bug — passes every test, surfaces as a reconciliation gap."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-claude-agents",
      "repository": "https://github.com/joshrkay/Serviceos",
      "path": ".claude/agents/track3-webhooks-idempotency.md",
      "ref": "90002670f77757eeb2194d020ca8225b11135125",
      "url": "https://github.com/joshrkay/Serviceos/blob/90002670f77757eeb2194d020ca8225b11135125/.claude/agents/track3-webhooks-idempotency.md",
      "key": "joshrkay/Serviceos/.claude/agents/track3-webhooks-idempotency.md"
    },
    "tools": [
      "Read",
      "Grep",
      "Glob"
    ],
    "model": "opus"
  },
  "instructions": "Find the Stripe webhook handler(s). Determine:\n\n- **Idempotency mechanism**: is there a dedupe on Stripe event ID? Is it\n  enforced at the **DB level** (unique constraint) or in **application code**\n  (racy)? What happens on redelivery of an already-processed event?\n- **Signature verification**: present, and does it **fail closed**?\n- **Event coverage**: are payment-intent, charge, and refund event types each\n  handled, and can any of them double-apply?\n- **Transaction boundary**: are webhook processing and the balance/status update\n  in one transaction, or can they partially commit?\n\nReport `",
  "cost": {
    "context_tokens": 170
  }
}

Fetch it by URL: GET /api/v1/registry/joshrkay-serviceos-track3-webhooks-idempotency-subagent/manifest?version=1.0.0

About

Use it

Manifest

Reviews