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.00311 | $0.01524 |
| Opus 5 | $0.00156 | $0.00762 |
| Sonnet 5 | $0.00062 | $0.00305 |
| Haiku 4.5 | $0.00031 | $0.00152 |
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 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 — 89 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 (EROD 9/2022 / dawniej WP250): 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), 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). Termin: 72 godziny.
- 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 terminie => zgłoszenie + wyjaśnienie opóźnienia (art. 33 ust. 1 zd. 2).
- Treść zgłoszenia (art. 33 ust. 3): charakter naruszenia (kategorie i przybliżona liczba osób oraz wpisów), dane kontaktowe IOD, możliwe konsekwencje, zastosowane/proponowane środki. Dopuszczalne zgłoszenie etapowe (art. 33 ust. 4).
- Skill podaje
deadline_72h(data+godzina) i przygotowuje draft wg pól formularza UODO.
Krok 4 - Zawiadomienie osób (art. 34)
Jeśli wysokie ryzyko => zawiadom osoby bez zbędnej zwłoki, językiem prostym i jasnym (art. 34 ust. 2: opis, IOD, konsekwencje, środki). Wyjątki (art. 34 ust. 3): odpowiednie zabezpieczenia (np. szyfrowanie czyniące dane nieczytelnymi), środki następcze eliminujące wysokie ryzyko, lub niewspółmierny wysiłek => komunikat publiczny.
What ships with it
1 file 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.
- 12d 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 (6 stars, last pushed 19d ago), licensed MIT. It adds 311 tokens to every session and 1,524 once invoked, about $0.0016 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-31.
Other skills, from other repositories
e-signature
Use when wiring an e-signature flow with DocuSign or Dropbox Sign — picking the SES/AES/QES legal tier, sending a PDF or template for signature, embedded signing, verifying signing webhooks, retrieving the signed PDF plus audit trail. NOT drafting contract text (that is contracts), NOT extracting fields from PDFs…
runtime-admissibility-review
Determines whether a specific AI-agent action, output, recommendation, or proposed commitment remains admissible for execution or institutional reliance under current authority, delegated scope, evidence, facts, policy, risk, escalation, and revocation conditions. Use this Skill before an enterprise or regulated AI…
agent-authority-charter-builder-arkadiy-miteiko
Creates an Agent Authority Charter for enterprise or regulated AI agents before deployment. Use this Skill when a user needs to define what an AI agent is allowed to do, who delegated authority to it, what actions are permitted or prohibited, when human approval is required, what evidence must be preserved, and how…
metago-compliance
A pre-task checklist for checking legal, ethical, and security concerns before acting. It covers privacy, copyright, permissions, sensitive data, system safety, and regional compliance requirements.
metago-thought-19-negentropy-engine
A framework for assessing whether a system has a positive or negative effect on social order, information clarity, trust, fairness, and innovation. It uses changes in these areas to discuss social responsibility and ethical risk.
metago-security-engineer
Security Engineer - specializes in security audit, penetration testing, vulnerability management, compliance checking, security design review, supply chain security, and incident response.