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 skills add roedyrustam/vibes-plug --skill doku-payment-gatewaygit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/roedyrustam/vibes-plug/doku-payment-gateway)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/doku-payment-gateway"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/doku-payment-gateway/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/doku-payment-gateway"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/doku-payment-gateway.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00071 | $0.02524 |
| Opus 5 | $0.00036 | $0.01262 |
| Sonnet 5 | $0.00014 | $0.00505 |
| Haiku 4.5 | $0.00007 | $0.00252 |
Grade A, and why
doku-payment-gateway 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 11d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DOKU Payment Gateway Integration / Integrasi Payment Gateway DOKU
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.
Description
Expert guide for implementing DOKU Payment Gateway (Jokul API v2) integrations based on official DOKU Developers Documentation. Covers authentication headers, SHA-256 Digest generation, HMAC-SHA256 request signature construction, Webhook notification verification, Checkout Payment Links, Direct Payments (Virtual Account, QRIS, E-Wallet, Credit Card), error handling, and sandbox/production deployment.
Trigger Conditions
Activate this skill when the user is:
- Building or refactoring DOKU Payment Gateway integration in Node.js, TypeScript, Python, Go, PHP, or Java.
- Implementing HMAC-SHA256 signature calculations or notification signature verification for DOKU API.
- Setting up DOKU Virtual Account (BCA, Mandiri, BRI, BNI, Permata, DOKU VA), QRIS, E-Wallet (OVO, ShopeePay, DANA, LinkAja), or Credit Card APIs.
- Debugging DOKU API authorization errors (e.g.,
Authorization Failed, invalid signature, incorrect timestamp format).
Core Architecture & Credentials
Environment Gateways
| Environment | Base URL | Dashboard Portal |
|---|---|---|
| Sandbox | https://api-sandbox.doku.com |
https://sandbox.doku.com |
| Production | https://api.doku.com |
https://dashboard.doku.com |
Mandatory Headers
Every request sent to DOKU API requires the following headers:
Client-Id: Merchant Client ID from DOKU Back Office.Request-Id: Unique random string generated for each request (e.g., UUID v4).Request-Timestamp: UTC ISO8601 timestamp string (e.g.,2026-08-07T13:00:00Z).Request-Target: Target API endpoint path (e.g.,/checkout/v1/paymentor/doku-virtual-account/v2/payment-code).Digest: Base64 encoded SHA-256 hash of the JSON payload string (Omitted forGETrequests).Signature: FormatHMACSHA256=<base64-signature>.
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.
- 11d ago First seen · 234 lines · 71 tokens per session scan A 839322dc7c8b
doku-payment-gateway is a skill published in the GitHub repository roedyrustam/vibes-plug (50 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 2,524 once invoked, about $0.0004 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
slickpay-integrator
An expert in integrating the Algerian SlickPay API (SATIM/EDAHABIA). Handles invoice creation, commission calculation, and webhooks securely.
cloudbase-wechat-integration
CloudBase WeChat integration guide for Mini Program WeChat Pay, Official Account JSAPI Pay, Native QR-code Pay, Official Account OAuth, openid handling, payment callbacks, and CloudBase Integration Center generated functions. This skill should be used when users ask to add, debug, or extend WeChat payment or…
api-and-interface-design
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
shopify-apps
Shopify app development - Remix, Admin API, checkout extensions.
commerce-app-business-config
Manage custom business configuration in an Adobe Commerce app. Use when the user wants to add, modify, or remove merchant-configurable settings (config fields, admin config, store configuration) exposed through Commerce Admin. Creates typed config fields (text, password, email, url, tel, boolean, list) in…
integrations
One-request, complete setup of external services — payment (Stripe, PromptPay, Omise, 2C2P), email, auth, analytics, storage and other integrations, including Thai-market services. Installs SDKs, creates API routes, env templates, and UI components in one pass. Use when the user asks to add payments, email, login…