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 panaversity/agentfactory-business-plugins --skill aml-typologiesgit clone --depth 1 https://github.com/panaversity/agentfactory-business-pluginsWrote 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/panaversity/agentfactory-business-plugins/aml-typologies)<a href="https://agentmods.dev/skills/panaversity/agentfactory-business-plugins/aml-typologies"><img src="https://agentmods.dev/badge/skills/panaversity/agentfactory-business-plugins/aml-typologies/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/panaversity/agentfactory-business-plugins/aml-typologies"><img src="https://agentmods.dev/badge/skills/panaversity/agentfactory-business-plugins/aml-typologies.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.00104 | $0.02383 |
| Opus 5 | $0.00052 | $0.01192 |
| Sonnet 5 | $0.00021 | $0.00477 |
| Haiku 4.5 | $0.00010 | $0.00238 |
Grade A, and why
aml-typologies 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 9d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
THE THREE STAGES OF MONEY LAUNDERING
Placement — Introducing illicit funds into the financial system Red flags: Large cash deposits; multiple deposits just below reporting threshold (structuring); money service business transactions; casino chip purchases/redemptions.
Layering — Obscuring the audit trail through multiple transactions Red flags: Rapid movement through multiple accounts; complex wire sequences across multiple jurisdictions; shell company or nominee director use; conversion between asset classes (cash → wire → crypto → real estate).
Integration — Re-introducing laundered funds as apparently legitimate income Red flags: Luxury asset purchases (real estate, vehicles, art); unexplained business investments; loan repayments from obscure sources; complex "business transactions" with no apparent commercial purpose.
TOP 20 AML TYPOLOGIES WITH DETECTION LOGIC
-
STRUCTURING (SMURFING) Indicator: Multiple cash deposits/withdrawals in a single account, each just below the reporting threshold, within a defined period. Detection rule: ≥3 transactions within 7 days each ≥ 80% of the reporting threshold. ML enhancement: Aggregate transactions per customer per rolling 30-day window. Note: The reporting threshold is jurisdiction-specific (USD 10,000 in USA, varies elsewhere).
-
ROUND-TRIPPING Indicator: Funds sent from Account A to Jurisdiction X, then returned from Jurisdiction X to Account A or a closely connected account within a short period. Detection: Wire-out to jurisdiction X followed by wire-in from same jurisdiction within 30 days, same approximate amount (±10%).
-
RAPID FUND MOVEMENT / VELOCITY Indicator: Account receives large funds then transfers them out within 24–72 hours with minimal balance remaining. Detection rule: Opening balance < 10% of daily inflow; >80% of incoming funds transferred out within 48 hours.
-
GEOGRAPHIC ANOMALY Indicator: Transactions to/from high-risk jurisdictions inconsistent with customer profile. Detection: Any transaction above de minimis to FATF grey-listed or black-listed countries. Enhanced scrutiny for: Iran, North Korea, Myanmar (FATF black list); current grey list — check FATF.org for current listing as it changes quarterly.
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.
- 9d ago First seen · 218 lines · 104 tokens per session scan A 2524cac3449c
aml-typologies is a skill published in the GitHub repository panaversity/agentfactory-business-plugins (29 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 104 tokens to every session and 2,383 once invoked, about $0.0005 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
fin-audit-support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
fin-sox-testing
Generate SOX sample selections, testing workpapers, and control assessments. Use when planning quarterly or annual SOX 404 testing, pulling a sample for a control (revenue, P2P, ITGC, close), building a testing workpaper template, or evaluating and classifying a control deficiency.
fin-journal-entry
Prepare journal entries with proper debits, credits, and supporting detail. Use when booking month-end accruals (AP, payroll, prepaid), recording depreciation or amortization, posting revenue recognition or deferred revenue adjustments, or documenting an entry for audit review.
audit-support
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
kyc-doc-parse
Parse an investor or client onboarding packet into structured KYC fields — identity, ownership, control, source of funds, and document inventory. Use as the first step of KYC screening; output feeds the rules engine.
regulatory-analysis
Analyzes documents and processes against FINRA, SEC, Federal Reserve, and CFPB regulatory frameworks. Identifies compliance gaps, classifies findings by severity, and recommends remediation. Use when performing compliance audits, regulatory reviews, gap analyses, or verifying policy adherence to financial regulations.