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 bobadilla-tech/requiems-api-skills --skill payments-intelligence-post-validategit clone --depth 1 https://github.com/bobadilla-tech/requiems-api-skillsWrote 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/bobadilla-tech/requiems-api-skills/payments-intelligence-post-validate)<a href="https://agentmods.dev/skills/bobadilla-tech/requiems-api-skills/payments-intelligence-post-validate"><img src="https://agentmods.dev/badge/skills/bobadilla-tech/requiems-api-skills/payments-intelligence-post-validate/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/bobadilla-tech/requiems-api-skills/payments-intelligence-post-validate"><img src="https://agentmods.dev/badge/skills/bobadilla-tech/requiems-api-skills/payments-intelligence-post-validate.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.00040 | $0.00732 |
| Opus 5.5 | $0.00016 | $0.00293 |
| Sonnet 5.5 | $0.00008 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
payments-intelligence-post-validate 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Endpoint
POST https://requiems.xyz/v1/systems/payment/validate
Validate Payment
Validate and cross-check BIN, IBAN, and SWIFT identifiers in one call. Returns per-field results and a consistency check that flags country and bank mismatches.
Parameters
| Name | Type | Required | Location | Description |
|---|---|---|---|---|
bin |
string | no | body | Card BIN (first 6–8 digits). At least one of bin, iban, or swift is required. |
iban |
string | no | body | IBAN string to validate. Checksum and format are verified. |
swift |
string | no | body | SWIFT/BIC code to look up institution and country. |
Request Example
{
"bin": "424242",
"iban": "DE89370400440532013000",
"swift": "DEUTDEDB"
}
Response Example
{
"data": {
"bin": {
"valid": true,
"scheme": "visa",
"card_type": "debit",
"card_level": "classic",
"country_code": "US",
"issuer": "JPMorgan Chase",
"prepaid": false,
"luhn_prefix_valid": true
},
"iban": {
"valid": true,
"country_code": "DE",
"bank_code": "37040044",
"account_number": "0532013000"
},
"swift": {
"valid": true,
"institution": "Deutsche Bank",
"country": "DE",
"branch": "Frankfurt"
},
"consistency": {
"ok": false,
"flags": ["country_mismatch_bin_iban"]
}
},
"metadata": {
"timestamp": "2026-01-01T00:00:00Z"
}
}
Response Fields
| Field | Type | Description |
|---|---|---|
bin |
object | BIN result. Null when bin was not provided. Contains valid, scheme, card_type, card_level, country_code, issuer, prepaid, luhn_prefix_valid. |
iban |
object | IBAN result. Null when iban was not provided. Contains valid, country_code, bank_code, account_number. |
swift |
object | SWIFT result. Null when swift was not provided. Contains valid, institution, country, branch. |
consistency.ok |
boolean | True when no cross-field mismatches were detected |
consistency.flags |
array | Mismatch flags. Possible values: country_mismatch_bin_iban, country_mismatch_bin_swift, country_mismatch_iban_swift, bank_mismatch_iban_swift |
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.
- 1mo ago First seen · 88 lines · 40 tokens per session scan A d048d4425aa9
payments-intelligence-post-validate is a skill published in the GitHub repository bobadilla-tech/requiems-api-skills (2 stars, last pushed 29d ago), licensed MIT. It adds 40 tokens to every session and 732 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-09-08.
Other skills, from other repositories
pier-cloud
This skill should be used when the user needs to consume the Pier Cloud (Lighthouse) API for cloud cost management — including JWT authentication, listing contexts, workspaces, workspace groups, and FinOps data views. Trigger whenever there is a need to integrate, automate, or debug calls to the Pier Cloud platform…
speckit.payment-fintech
FinTech & Payment Systems Engineer - Idempotency ledger, payment gateways, signature verification, and financial transaction state machines.
loan-covenant-review
Run a quarterly loan covenant compliance review: covenant table with required vs actual vs headroom, trend and trajectory-to-breach analysis, waiver and amendment options with pricing implications, early-warning indicators, and a watch-list recommendation. Use when asked to review covenant compliance, check covenant…
expense-policy
Write a clear company expense & reimbursement policy. Use when asked to write an expense policy, a reimbursement policy, a travel & expense (T&E) policy, or spending guidelines. Produces a practical policy — what's covered, limits by category, the approval and submission process, timelines, and what's not reimbursable…
comptable
Comptabilité, fiscalité et facturation pour entreprises françaises. Gère écritures PCG, déclarations TVA, IS/IR, clôture annuelle, liasse fiscale (2033/2065), FEC, états financiers, et chaîne facturation (mentions obligatoires, numérotation, Factur-X/UBL/CII, plateformes agréées PDP/PA, e-reporting, réforme 2026…
commissaire-aux-comptes
Commissaire aux comptes IA pour l'audit des comptes annuels d'entreprises françaises. Applique la démarche NEP en 7 phases : prise de connaissance, contrôle du FEC, vérification du bilan, du compte de résultat, de la balance, de la liasse fiscale, et contrôles transversaux. Émet une opinion motivée sur la fiabilité…