integrate-midtrans-payments

integrate-midtrans-payments is a skill for Codex from veritrans/midtrans-agent-skills. It costs 137 tokens per session (2,341 once invoked), scanned A, original, BSD-3-Clause.

A skill for integrating Midtrans, a payment gateway, into an application. It covers checkout, payment APIs, payment methods, callbacks, testing, and the surrounding account, security, and deployment decisions.

In plain words
What is it for?
Use it to build or troubleshoot Midtrans payments such as Snap checkout, cards, QRIS, virtual accounts, GoPay, ShopeePay, DANA, and related products. It also supports sandbox verification, callback handling, and integration review.
Why use it?
Payment integrations can fail through incorrect states, duplicate callbacks, weak credential handling, or untested merchant settings. The skill requires checking the real checkout design and current Midtrans documentation before implementation.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex; mentions OpenCode.

Good fit Use it to build or troubleshoot Midtrans payments such as Snap checkout, cards, QRIS, virtual accounts, GoPay, ShopeePay, DANA, and related products. It also supports sandbox verification, callback handling, and integration review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/veritrans/midtrans-agent-skills/integrate-midtrans-payments
Install

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.

Any agent
npx skills add veritrans/midtrans-agent-skills --skill integrate-midtrans-payments
Clone the repo
git clone --depth 1 https://github.com/veritrans/midtrans-agent-skills

Made for: Codex.

Wrote 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.

agentmods badge for integrate-midtrans-payments

README.md
[![agentmods](https://agentmods.dev/badge/skills/veritrans/midtrans-agent-skills/integrate-midtrans-payments/github.svg)](https://agentmods.dev/skills/veritrans/midtrans-agent-skills/integrate-midtrans-payments)
Your own site
<a href="https://agentmods.dev/skills/veritrans/midtrans-agent-skills/integrate-midtrans-payments"><img src="https://agentmods.dev/badge/skills/veritrans/midtrans-agent-skills/integrate-midtrans-payments/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.

agentmods 80×15 button for integrate-midtrans-payments

Your own site · 80×15
<a href="https://agentmods.dev/skills/veritrans/midtrans-agent-skills/integrate-midtrans-payments"><img src="https://agentmods.dev/badge/skills/veritrans/midtrans-agent-skills/integrate-midtrans-payments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 137 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,341 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00137 $0.02341
Opus 5.5 $0.00055 $0.00936
Sonnet 5.5 $0.00027 $0.00468
Haiku 4.5 $0.00014 $0.00234

Measured 2mo ago against content hash 60f8e7cbcb2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

integrate-midtrans-payments 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 2mo ago.

The scan reads SKILL.md. This mod also ships 9 executable files (scripts/bisnap_timestamp.py, scripts/dry_run_bisnap_sign.py, scripts/format_partner_service_id.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

integrate-midtrans-payments/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Integrate Midtrans Payments

Operating Rule

Treat this as payment-system integration, not generic API wiring. Before changing code, learn the merchant's checkout architecture, payment products, persistence model, callback paths, auth/session boundary, environment management, deployment target, and test harness.

Before recommending a Midtrans product or writing code, complete the merchant readiness preflight: account state, sandbox credentials, active payment methods, expected customer flows, dashboard callback URLs, and the proof level the merchant expects. If those facts are missing and cannot be inferred from the project, pause and ask for them instead of silently assuming them.

Use current Midtrans docs each time. Search https://docs.midtrans.com/llms.txt first, then open product pages for the methods being implemented; llms.txt links the .md variant of every page — fetch those instead of the HTML.

Precedence: live docs.midtrans.com content wins over this skill for endpoints, parameters, field names, and product availability; this skill wins for integration discipline (state model, idempotency, signature hygiene, verification). Skill version 0.3.2, validated against docs.midtrans.com on 2026-06-25. If a current docs page contradicts this skill, follow the docs and ask the merchant to report the mismatch at https://github.com/veritrans/midtrans-agent-skills/issues.

Workflow

  1. Run merchant readiness preflight

    • Complete merchant-readiness-preflight.md before product choice or code.
    • Infer from env, deploy config, runbooks, tests, provider code, and specs; ask only for missing blockers.
    • Gate unavailable methods with configuration and state what dashboard/merchant action is still required.
  2. Classify the integration

    • Identify whether the merchant wants hosted checkout, custom UI, recurring/tokenized payments, marketplace/partner behavior, or a hybrid.
    • Map each requested payment method to the intended Midtrans product before writing code.
    • Do not mix Snap, Core API, and BI-SNAP request shapes, auth headers, callback semantics, or status objects.
    • If the merchant need is unclear, read merchant-decision-tree.md and ask the smallest set of clarifying questions.

Read the full file on GitHub · 113 lines

Files

What ships with it

41 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 2mo ago First seen · 113 lines · 137 tokens per session scan A 60f8e7cbcb2a

Subscribe to this mod's changes

integrate-midtrans-payments is a skill published in the GitHub repository veritrans/midtrans-agent-skills (12 stars, last pushed 4mo ago), licensed BSD-3-Clause. It adds 137 tokens to every session and 2,341 once invoked, about $0.0005 per session on Opus 5.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-31.

Related

integrate-midtrans-payments compared with skills from other repositories

integrate-midtrans-payments next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
integrate-midtrans-paymentsveritrans/midtrans-agent-skillsSkill124mo agoBSD-3-ClauseA137Codex
asc-ppp-pricingrorkai/app-store-connect-cli-skillsSkill1.1kyesterdayMITA45Claude Code
snaplii-cliSnaplii-Inc/agent-to-merchant-paymentsSkill8122d agoApache-2.0A184Claude Code
stripeCraftOS-dev/CraftBotSkill4022d agoMITA79Claude Code, Codex
ai-slopwaybarrios/opencode-power-packSkill5515d agoMITA61Claude Code
stripemagnus919/agent-skillsSkill1662d agoMITA116Claude Code, Codex
asc-ppp-pricinghanamizuki/solopreneurSkill1563d agoMITA45Claude Code