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 bromso/metapowers --skill bank-partnershipgit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/bank-partnership)<a href="https://agentmods.dev/skills/bromso/metapowers/bank-partnership"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/bank-partnership/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/bromso/metapowers/bank-partnership"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/bank-partnership.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.00015 | $0.01135 |
| Opus 5 | $0.00008 | $0.00567 |
| Sonnet 5 | $0.00003 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
bank-partnership 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 10d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bank Partnership Compliance Assessment
Assess partner bank compliance requirements for "$ARGUMENTS". Evaluate regulatory expectations for bank-fintech partnerships, compliance management system pass-through, and examination readiness.
Prerequisites
Read .metapowers/compliance/$ARGUMENTS/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "$ARGUMENTS". Run
/compliance:regulatory-landscape $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check.
Process
-
Read context files:
- Read
plugins/compliance/shared/grc-lifecycle-guide.mdfor GRC methodology reference - Read
plugins/compliance/shared/assessment-template.mdfor output structure - Read
.metapowers/compliance/$ARGUMENTS/00-scope.mdfor scope and control framework context
- Read
-
Regulatory expectations for bank-fintech partnerships:
- Assess alignment with OCC Third-Party Risk Management guidance (OCC 2013-29, 2023-17)
- Evaluate compliance with FDIC Financial Institution Letters on third-party relationships
- Review Federal Reserve SR 13-19 guidance applicability
- Assess interagency guidance on third-party relationships (June 2023)
- Evaluate how the partnership model maps to regulatory definitions (critical activity, significant bank function)
-
Compliance management system requirements:
- Assess compliance management system (CMS) components passed through from partner bank
- Evaluate board/management oversight requirements imposed on the fintech
- Review compliance policies and procedures mandated by the bank partner
- Assess compliance monitoring and testing expectations
- Evaluate complaint management and consumer response requirements
-
Consumer compliance obligations:
- Assess UDAP (Section 5 of FTC Act) compliance in product design and marketing
- Evaluate UDAAP (Dodd-Frank Act) compliance for unfair, deceptive, or abusive acts or practices
- Review fair lending compliance (ECOA, Fair Housing Act) in credit products
- Assess Community Reinvestment Act (CRA) implications and data reporting
- Evaluate Truth in Lending (TILA), Truth in Savings (TISA), EFTA/Reg E compliance
- Review fair debt collection practices where applicable
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.
- 10d ago First seen · 100 lines · 15 tokens per session scan A 5f61822b933c
bank-partnership is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 1,135 once invoked, about $0.0001 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-31.
Other skills, from other repositories
internal-controls-and-audit
Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is…
capital-structure-and-covenants
Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to…
revenue-recognition
Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms…
tax
Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check…
laravel-stripe-connect
Use when implementing multi-vendor marketplace payments, seller onboarding, commissions, payouts, or split payments with Stripe Connect.
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é…