T09 · Insecure Skill Coding Practices
- Location
webhooks.md:96- Finding
Webhook Events Are Acknowledged Before Durable Processing
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent billing-integration guidance skill, but it includes copyable high-impact payment examples with insufficient guardrails and a few unsafe financial implementation patterns.
Review the examples before using this skill in production billing work. Use Stripe/Paddle test mode first, require explicit approval before actions that charge, refund, send invoices, alter subscriptions, or update connected accounts, and replace the unsafe webhook, refund, and floating-point billing examples with durable, audited, integer-money implementations.
webhooks.md:96Webhook Events Are Acknowledged Before Durable Processing
webhooks.md:102Webhook Endpoint Reflects Internal Exception Messages
marketplace.md:98Marketplace Split-Refund Example Returns Only Half of the Requested Refund
usage-billing.md:110Usage Billing Performs Monetary Calculations with Floating-Point Values
Line L102 contains instructional content in Spanish while the rest of the skill is in English. This introduces a language/locale inconsistency without any user opt-in or documented reason, which can violate language policy expectations and reduce accessibility for users expecting a single language.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
### Operational Errors
- Sending payment reminders during contractual grace period
- Dunning without checking for open disputes → double loss
- Proration without specifying mode → unexpected customer charges
- Refunding without checking for existing chargeback → paying twice
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
### Operational Errors
- Sending payment reminders during contractual grace period
- Dunning without checking for open disputes → double loss
- Proration without specifying mode → unexpected customer charges
- Refunding without checking for existing chargeback → paying twice
This markdown file includes example onboarding code that updates an account with personally sensitive information such as ssn_last_4 and even notes that a full SSN may be collected. The surrounding documentation does not warn readers about privacy, secure handling, or compliance obligations when collecting this data.
This markdown file provides copyable Stripe examples that create checkout sessions, confirm off-session payment intents, create subscriptions, apply coupons, and finalize/send invoices, all of which can affect customer billing and account state. The document does not include any user-facing warning that these actions may create charges, alter subscriptions, or send invoices if run against live data.
In this markdown file, the embedded code example performs a network request to an external government API and includes the VAT number in the request body. The surrounding documentation does not warn that entered VAT identifiers and related data will be transmitted off-system, which is relevant to privacy and compliance expectations.