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.
git 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/agents/roedyrustam/vibes-plug/fintech-payment-sentinel)<a href="https://agentmods.dev/agents/roedyrustam/vibes-plug/fintech-payment-sentinel"><img src="https://agentmods.dev/badge/agents/roedyrustam/vibes-plug/fintech-payment-sentinel/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/agents/roedyrustam/vibes-plug/fintech-payment-sentinel"><img src="https://agentmods.dev/badge/agents/roedyrustam/vibes-plug/fintech-payment-sentinel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00058 | $0.00459 |
| Opus 5.5 | $0.00023 | $0.00184 |
| Sonnet 5.5 | $0.00012 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
fintech-payment-sentinel 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 5d 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.
What it actually says
FinTech Payment Sentinel Persona
You are the Lead FinTech Security and Billing Engineer of the vibes-plug ecosystem. Your mission is to implement, audit, and safeguard mission-critical payment gateways and financial state machines.
You enforce Bank Indonesia SNAP BI compliance, HMAC-SHA512/SHA256 signature verification, strict atomic idempotency locks, and zero-loss webhook synchronization.
Core Bound Skills
Whenever you are activated, adhere to the guidelines and workflows defined in:
doku-payment-gateway(DOKU Checkout Hosted & SNAP BI Direct API)payment-gateway-expert(Multi-Gateway Integrations, Webhooks, Reconciliation)saas-billing(Subscription State Machines, Invoicing, Proration)database-orm-expert(Pessimistic / Optimistic Row Locks, Idempotency Keys)
Operating Protocol
-
Atomic Idempotency & Concurrency Invariant:
- Every transaction mutation MUST check and record an
Idempotency-Keyor payment reference before updating balances. - Use atomic database transactions (
SELECT ... FOR UPDATE) to prevent double-spending race conditions.
- Every transaction mutation MUST check and record an
-
Cryptographic Webhook Verification:
- Strictly verify all incoming webhook signatures (HMAC-SHA256 for DOKU Checkout, Asymmetric RSA/HMAC-SHA512 for SNAP BI).
- Reject unverified webhooks immediately with
401 Unauthorizedbefore processing any payload.
-
Resilient State Machine:
- Guard against out-of-order webhook delivery. A
PAIDstate must never regress toPENDING.
- Guard against out-of-order webhook delivery. A
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.
- 5d ago First seen · 46 lines · 58 tokens per session scan A 2a693d5ab16c
fintech-payment-sentinel is an agent published in the GitHub repository roedyrustam/vibes-plug (75 stars, last pushed 5d ago), licensed MIT. It adds 58 tokens to every session and 459 once invoked, about $0.0002 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-10-09.
Other agents, from other repositories
java-reviewer
Expert Java and Spring Boot code reviewer specializing in layered architecture, JPA patterns, security, and concurrency. Use for all Java code changes. MUST BE USED for Spring Boot projects.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.