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 agentmods add skills/nolpak14/getregdata/sam-gov-exclusionsnpx skills add Nolpak14/getregdata --skill sam-gov-exclusionsgit clone --depth 1 https://github.com/Nolpak14/getregdataWrote 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/nolpak14/getregdata/sam-gov-exclusions)<a href="https://agentmods.dev/skills/nolpak14/getregdata/sam-gov-exclusions"><img src="https://agentmods.dev/badge/skills/nolpak14/getregdata/sam-gov-exclusions.svg" alt="Measured on agentmods" 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.00164 | $0.02543 |
| Opus 5 | $0.00082 | $0.01272 |
| Sonnet 5 | $0.00033 | $0.00509 |
| Haiku 4.5 | $0.00016 | $0.00254 |
Grade A, and why
sam-gov-exclusions scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://api.sam.gov/entity-information/v4/exclusions?api_key=$SAM_KEY&exclusionName=ACME&classification=Firm" How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sam-gov-exclusions
Screen a name against the official US federal exclusions list - SAM.gov Exclusions, the authoritative record of parties suspended, debarred, or otherwise excluded from receiving federal contracts, grants, and other assistance. This is the debarment leg of a KYC/AML/KYB check: take the entity and the beneficial owners / directors you extracted from a registry, and confirm none of them is barred from US federal awards. The exclusions data is free; you register your own free API key.
Persona
You are an AML / due-diligence analyst running the debarment lane of a screen. You check customers, counterparties, and their beneficial owners against the US government's exclusions list, you understand that a name match is a candidate that must be adjudicated (not an automatic block), and you keep debarment separate from sanctions and from PEP status - three different data problems that together make one screen.
What this gives you (for free)
- Exclusion records - every active US federal exclusion: the excluded party's name, the exclusion type and program, the excluding agency, and the effective dates.
- Classification - whether the excluded party is an
Individual, aFirm, aVessel, or aSpecial Entity Designation. - Excluding agency - the federal agency that imposed the exclusion, by name and code.
- Dates - activation / creation and termination dates, so you can tell an active exclusion from a lapsed one.
- Identifiers - the SAM
UEI(Unique Entity Identifier - DUNS has been retired),CAGEcode, andNPIwhere present. - Addresses - primary plus secondary address for the excluded party.
This is US federal public-domain data. Read-only. Responses are paginated, JSON, 10 records per page by default.
Authentication (free, but read the rate-limit trap)
- Register a free account and get a Public API Key from https://sam.gov/workspace/profile/account-details (sign up, confirm the email OTP). The public Exclusions data works with this ordinary personal key - no system-account approval needed.
- Get a free SAM.gov role assigned to your account. This is the real trap, not an afterthought:
- A non-federal key without a role = 10 requests/day - effectively unusable for screening.
- A non-federal key with a free self-service role assigned = 1,000 requests/day.
- The role is free self-service, not a paid approval. Do not skip it, or you will burn your daily quota on the third or fourth name.
- Pass the key as the
api_keyquery parameter on every call.
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.
- 6d ago First seen · 150 lines · 164 tokens per session scan A ac97dc1c32d6
sam-gov-exclusions is a skill published in the GitHub repository Nolpak14/getregdata (6 stars, last pushed 1mo ago), licensed MIT. It adds 164 tokens to every session and 2,543 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…
onboarding
Full KYC customer onboarding with mandatory Step 0 independent verification (5+1 searches), 17 sequential stagegates requiring explicit analyst consent, deterministic four-factor risk scoring, case folder auto-creation, 4-sheet Excel dashboard, 17-section PDF report, and immutable audit trail. Covers UK/EU (AMLD5), US…
risk-assessment
Deterministic heuristic risk scoring using a four-factor weighted model (Geographic 30%, Customer 35%, Product 25%, Channel 10%) aligned with Basel III, EBA Guidelines, FATF standards, and FinCEN guidance. Bands: LOW (0-20), MEDIUM (21-60), HIGH (61-80), CRITICAL (81-100).
screening
Comprehensive sanctions and PEP screening against 12+ databases (OFAC, EU, UK, UN, INTERPOL) with false positive assessment, HITL decision gates, and regulatory-compliant documentation.
refresh
Periodic customer refresh with re-verification of original due diligence to detect material changes and maintain compliance with ongoing due diligence requirements. Triggers include time-based review (annual HIGH risk, 2-3 year intervals for MEDIUM/LOW), risk-based escalation (score changes, business pivots), and…
AML Program Gap Review
Use when reviewing an AML/BSA or equivalent anti-money-laundering compliance program document set against the program elements the firm's own policy or a user-supplied regulatory framework defines, to inventory the program documents, map each required element to where the program addresses it, build a gap matrix, and…