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 matematicsolutions/awesome-matematic-skills-pl --skill rodo-naruszenie-72h-plgit clone --depth 1 https://github.com/matematicsolutions/awesome-matematic-skills-plWrote 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/matematicsolutions/awesome-matematic-skills-pl/rodo-naruszenie-72h-pl)<a href="https://agentmods.dev/skills/matematicsolutions/awesome-matematic-skills-pl/rodo-naruszenie-72h-pl"><img src="https://agentmods.dev/badge/skills/matematicsolutions/awesome-matematic-skills-pl/rodo-naruszenie-72h-pl/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/matematicsolutions/awesome-matematic-skills-pl/rodo-naruszenie-72h-pl"><img src="https://agentmods.dev/badge/skills/matematicsolutions/awesome-matematic-skills-pl/rodo-naruszenie-72h-pl.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.00327 | $0.02460 |
| Opus 5.5 | $0.00131 | $0.00984 |
| Sonnet 5.5 | $0.00065 | $0.00492 |
| Haiku 4.5 | $0.00033 | $0.00246 |
Grade A, and why
rodo-naruszenie-72h-pl 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 17d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RODO Naruszenie 72h PL - obsługa naruszenia ochrony danych (art. 33-34)
Filozofia
Przy naruszeniu liczy się zegar i dowód rozumowania. Skill prowadzi udokumentowane drzewo decyzyjne i składa drafty; decyzję o zgłoszeniu i wysyłkę podejmuje administrator/IOD. Zero domyślania - jeśli brak danych do oceny ryzyka, skill to oznacza jako lukę, nie zgaduje.
Krok 1 - Czy to naruszenie i jaki typ
Naruszenie = naruszenie bezpieczeństwa prowadzące do przypadkowego/niezgodnego z prawem zniszczenia, utraty, modyfikacji, nieuprawnionego ujawnienia lub dostępu (art. 4 pkt 12). Sklasyfikuj: poufność (ujawnienie/dostęp), integralność (modyfikacja), dostępność (utrata/zniszczenie). Często łączone.
Krok 2 - Ocena ryzyka dla praw i wolności
Czynniki (wytyczne EROD 9/2022, zaktualizowana wersja WP250 rev.01): typ naruszenia,
charakter/wrażliwość/wolumen danych, łatwość identyfikacji, waga skutków (kradzież tożsamości,
strata finansowa, dyskryminacja, szkoda reputacyjna), cechy szczególne osób (dzieci, pacjenci),
cechy szczególne administratora (np. placówka medyczna), liczba osób. Wynik: ryzyko: brak / istnieje / wysokie.
Krok 3 - Zgłoszenie do UODO (art. 33) - LICZNIK 72h
- Zegar startuje od STWIERDZENIA naruszenia (nie od zdarzenia). Zgłoś bez zbędnej zwłoki, w miarę możliwości nie później niż w terminie 72 godzin (art. 33 ust. 1) - 72 godziny to granica, nie cel.
- Zgłaszaj, chyba że jest mało prawdopodobne, by naruszenie skutkowało ryzykiem dla praw i wolności (art. 33 ust. 1). Brak zgłoszenia => uzasadnij i udokumentuj.
- Po 72 godzinach => zgłoszenie + wyjaśnienie przyczyn opóźnienia (art. 33 ust. 1 zd. 2).
- Treść zgłoszenia, co najmniej (art. 33 ust. 3): charakter naruszenia (w miarę możliwości kategorie i przybliżona liczba osób oraz wpisów), imię i nazwisko oraz dane kontaktowe IOD lub oznaczenie innego punktu kontaktowego, możliwe konsekwencje, środki zastosowane lub proponowane (w stosownych przypadkach także minimalizujące skutki). Dopuszczalne zgłoszenie etapowe, gdy nie wszystko wiadomo od razu, sukcesywnie bez zbędnej zwłoki (art. 33 ust. 4).
- Skill podaje
deadline_72h(data+godzina) i przygotowuje draft wg pól formularza UODO.
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.
- 17d ago Changed · +10 lines · +16 tokens per session aab8c6ded24b
- 21d ago Changed · +21 lines 374952b79d72
- 1mo ago First seen · 89 lines · 311 tokens per session scan A ccb692f3da5e
rodo-naruszenie-72h-pl is a skill published in the GitHub repository matematicsolutions/awesome-matematic-skills-pl (8 stars, last pushed 8d ago), licensed MIT. It adds 327 tokens to every session and 2,460 once invoked, about $0.0013 per session on Opus 5.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
mqc-timeline-master
Turn raw case materials into a faithful, court-ready case timeline (SVG + PNG + PPTX + VSDX + drawio, plus a traceability index in Word). Use this whenever the user hands over litigation materials — a judgment, complaint, defence, evidence list, contract, bank or Alipay statement, WeChat screenshots, scanned exhibits…
mqc-litigation-visual-redraw
Redraw a litigation diagram into a restrained, court-ready presentation graphic (SVG + PNG) WITHOUT changing any text or legal meaning. Use this whenever the user supplies a case timeline, a legal process flowchart, OR a party/relationship diagram and wants it cleaned up, beautified, redrawn, made professional…
universal-standards
LegalAnt operating protocol — HITL gates, citation completeness, hallucination defence, Indian law default, data security, and mandatory disclaimer. Applies to every agent on every matter.
niw-package-review
Reviews an assembled EB-2 NIW petition package before filing, as a skeptical adjudicator would. Reads the actual exhibits, recommendation letters and petition draft, tests each Dhanasar prong against the preponderance standard on documented evidence only, quotes the specific petition passages that overclaim, and…
niw-rfe-response
Works a USCIS Request for Evidence or Notice of Intent to Deny on an EB-2 NIW petition, from reading the notice through to a drafted response. Reads the printed deadline rather than computing one, crosswalks each contested issue against the record as actually filed, stops for the petitioner to correct what it found…
indian-law-defaults
Indian statute and regulatory hierarchy defaults. All agents assume Indian jurisdiction unless overridden. Auto-triggers FEMA for foreign counterparties and SEBI LODR for listed entities.