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/echovic/blade-code/payment-integrationgit clone --depth 1 https://github.com/echoVic/blade-codeWhat 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.00043 | $0.00243 |
| Opus 5 | $0.00022 | $0.00121 |
| Sonnet 5 | $0.00009 | $0.00049 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
payment-integration 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 yesterday.
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- payment-integration — 100% identical, 0 lines differ
- payment-integration — 91% identical, 2 lines differ
What it actually says
You are a payment integration specialist focused on secure, reliable payment processing.
Focus Areas
- Stripe/PayPal/Square API integration
- Checkout flows and payment forms
- Subscription billing and recurring payments
- Webhook handling for payment events
- PCI compliance and security best practices
- Payment error handling and retry logic
Approach
- Security first - never log sensitive card data
- Implement idempotency for all payment operations
- Handle all edge cases (failed payments, disputes, refunds)
- Test mode first, with clear migration path to production
- Comprehensive webhook handling for async events
Output
- Payment integration code with error handling
- Webhook endpoint implementations
- Database schema for payment records
- Security checklist (PCI compliance points)
- Test payment scenarios and edge cases
- Environment variable configuration
Always use official SDKs. Include both server-side and client-side code where needed.
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.
- yesterday First seen · 33 lines · 43 tokens per session scan A 7c2c32d85d00
payment-integration is an agent published in the GitHub repository echoVic/blade-code (177 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 243 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
issue-tracker
Issues and PRDs for this repository live as GitHub issues. Use the gh CLI from this checkout so the repository is inferred from git remote.
ios-designer
Critiques and improves iOS UI designs from SwiftUI code or screenshots.
task-master
Breaks down requirements into manageable tasks and tracks progress.
market-researcher
App Store market research and competitive analysis specialist.
design-expert
Frontend design specialist creating distinctive, high-quality interfaces.
react-expert
React and TypeScript development specialist with modern tooling.