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 vyayasan/kyc-analyst --skill transaction-monitoringgit clone --depth 1 https://github.com/vyayasan/kyc-analystWrote 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/vyayasan/kyc-analyst/transaction-monitoring)<a href="https://agentmods.dev/skills/vyayasan/kyc-analyst/transaction-monitoring"><img src="https://agentmods.dev/badge/skills/vyayasan/kyc-analyst/transaction-monitoring/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/vyayasan/kyc-analyst/transaction-monitoring"><img src="https://agentmods.dev/badge/skills/vyayasan/kyc-analyst/transaction-monitoring.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.00047 | $0.00745 |
| Opus 5 | $0.00023 | $0.00373 |
| Sonnet 5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
transaction-monitoring 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 12d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transaction Monitoring Skill - v1.0.0
AML transaction monitoring for ongoing customer relationships. Identifies suspicious patterns, assesses structuring and layering, and prepares Suspicious Activity Reports (SARs).
Overview
Transaction monitoring is a continuous obligation under AML regulations. This skill analyzes transaction data to detect patterns that may indicate money laundering, terrorist financing, or other financial crime.
Detection Patterns
1. Structuring (Smurfing)
- Multiple transactions just below reporting thresholds
- Multiple deposits across different branches/channels on same day
- Pattern of round-number transactions
- Threshold (US): $10,000 CTR threshold; $5,000 aggregated suspicious activity
2. Layering
- Complex routing through multiple accounts or entities
- Rapid movement between accounts with no clear business purpose
- International transfers through multiple jurisdictions
- Use of shell companies or nominee accounts
3. Circular Flows
- Money leaving and returning to same account via intermediaries
- Round-trip transactions with no economic substance
- Funds flowing through subsidiaries back to parent
4. Velocity Anomalies
- Sudden increase in transaction frequency
- Dramatic change in average transaction value
- Activity inconsistent with customer profile or declared business
- Dormant account reactivation with high-value activity
5. Geographic Risk Patterns
- Transactions to/from FATF grey-list or black-list jurisdictions
- Unexplained payments to/from high-risk countries
- Wire transfers to known shell company jurisdictions
Monitoring Process
Step 1: Data Analysis
- Import transaction data (CSV, Excel, or database extract)
- Calculate baseline metrics (average value, frequency, counterparties)
- Identify deviations from customer profile
Step 2: Pattern Detection
- Apply detection rules for each pattern type
- Flag transactions meeting alert criteria
- Score alerts by severity (LOW/MEDIUM/HIGH/CRITICAL)
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.
- 12d ago First seen · 101 lines · 47 tokens per session scan A 8762808bde1f
transaction-monitoring is a skill published in the GitHub repository vyayasan/kyc-analyst (56 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 745 once invoked, about $0.0002 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
regtech-expert
Expert in regulatory technology, compliance automation, KYC/AML, transaction monitoring, risk assessment, and automated reporting. Use when the user mentions compliance, KYC, AML, transaction monitoring, risk assessment, or regulatory reporting, or when the task involves KYC/AML Compliance, KYC/AML Program, Regulatory…
ainumbers
Deterministic regulatory-computation estate: 640+ compliance tools, chains, a verify ledger, and a timestamping anchor, callable over MCP with zero-egress in-page twins. Rules: synthetic data only; verify with verifyexecutionhash before trusting; return a ledger link; never paste PII. MCP: https://mcp.ainumbers.co/mcp.
deepidv-verify
Identity verification, KYC, face liveness, deepfake detection, adverse media screening, and AML/sanctions checks via the deepidv API. Use when a user needs to verify someone's identity, check if media is AI-generated, screen for sanctions/PEP status, or run adverse media checks.
compliance-documentation-requirements
Use when setting up or auditing how compliance documentation is structured, collected, and preserved for regulatory audit in Salesforce FSC — covering KYC data collection workflows, AML screening integration setup, audit trail configuration, and regulatory reporting readiness. Triggers: KYC form setup, AML integration…
compliance-documentation-requirements
Use when setting up or auditing how compliance documentation is structured, collected, and preserved for regulatory audit in Salesforce FSC — covering KYC data collection workflows, AML screening integration setup, audit trail configuration, and regulatory reporting readiness. Triggers: KYC form setup, AML integration…
skill
name: ainumbers description: Deterministic regulatory-computation estate: 640+ compliance tools, chains, a verify ledger, and a timestamping anchor, callable over MCP with zero-egress in-page twins. Rules: synthetic data only; verify with verifyexecutionhash before trusting; return a ledger link; never paste PII. MCP…