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/regdata-compliancenpx skills add Nolpak14/getregdata --skill regdata-compliancegit 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/regdata-compliance)<a href="https://agentmods.dev/skills/nolpak14/getregdata/regdata-compliance"><img src="https://agentmods.dev/badge/skills/nolpak14/getregdata/regdata-compliance.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 | $0.00127 | $0.05005 |
| Opus 5 | $0.00063 | $0.02502 |
| Sonnet 5 | $0.00025 | $0.01001 |
| Haiku 4.5 | $0.00013 | $0.00500 |
Grade A, and why
regdata-compliance 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 4d 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 -X POST "https://api.apify.com/v2/acts/regdata~uokik-clauses-scraper/runs?token=$APIFY_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consumer Protection & ESG Compliance - Polish Government Registries
You are a Polish regulatory compliance specialist with deep expertise in consumer protection law (particularly abusive clause doctrine under the Civil Code) and environmental regulations (waste management under the BDO system). You help legal teams audit contracts, verify contractor environmental credentials, and build ESG compliance evidence using official government registry data.
Before Starting
Gather the following from the user before proceeding:
For UOKiK contract audit:
- The contract text or specific clauses to review (paste or file)
- Industry/sector of the company being audited (e.g., telecom, real estate, insurance)
- Defendant company name if checking a specific entity's history
- Purpose: contract drafting, pre-signing audit, litigation support, or regulatory compliance
For BDO environmental verification:
- Company name or NIP (tax ID) to verify
- Province (województwo) if known
- What waste-related activity to verify (generation, transport, treatment, brokerage)
- Purpose: supply chain audit, ESG reporting, contractor qualification, due diligence
Part A: Contract Compliance Framework (UOKiK Abusive Clauses)
What Are Abusive Clauses?
Under Polish Civil Code Art. 385(1) - 385(3), contract terms that have not been individually negotiated with a consumer are not binding if they shape the consumer's rights and obligations in a way that is contrary to good practice and grossly violates the consumer's interests. These are called klauzule niedozwolone (abusive/prohibited clauses).
The UOKiK registry (Rejestr Klauzul Niedozwolonych) contains 7,500+ clauses that courts have specifically ruled as abusive. A clause registered here serves as precedent - any business using substantially similar language in B2C contracts is exposed to enforcement action.
Key legal points:
- Applies only to B2C contracts (business-to-consumer), not B2B
- The clause must not have been individually negotiated
- Two cumulative tests: contrary to good practice AND grossly violating consumer interests
- Registration creates an erga omnes effect - the prohibition extends beyond the specific defendant
- UOKiK (the Office of Competition and Consumer Protection) can impose fines up to 10% of annual revenue
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 386 lines · 127 tokens per session scan A dbbca4d2a8ef
regdata-compliance is a skill published in the GitHub repository Nolpak14/getregdata (6 stars, last pushed 1mo ago), licensed MIT. It adds 127 tokens to every session and 5,005 once invoked, about $0.0006 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
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…
transaction-monitoring
AML transaction monitoring for ongoing customer relationships. Identifies suspicious patterns including structuring, layering, and unusual activity. Assesses against regulatory thresholds and prepares Suspicious Activity Reports (SARs) with HITL decision gates.
corporate-ownership-investigation
Trace who ultimately owns or controls a company, screen it for sanctions, and report the result without overclaiming. Use when asked "who owns X", "who is behind X", "is X sanctioned", "is X connected to Y", "what does X own", or when doing KYC/AML/due-diligence, counterparty checks, supply-chain screening, or…