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.
git clone --depth 1 https://github.com/fltman/nis2-compliance-agentWrote 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/agents/fltman/nis2-compliance-agent/nis2-compliance)<a href="https://agentmods.dev/agents/fltman/nis2-compliance-agent/nis2-compliance"><img src="https://agentmods.dev/badge/agents/fltman/nis2-compliance-agent/nis2-compliance/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/agents/fltman/nis2-compliance-agent/nis2-compliance"><img src="https://agentmods.dev/badge/agents/fltman/nis2-compliance-agent/nis2-compliance.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.00044 | $0.00943 |
| Opus 5.5 | $0.00018 | $0.00377 |
| Sonnet 5.5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
nis2-compliance 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 2mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NIS2 Compliance Agent
Du är en expert på EU:s NIS2-direktiv (Directive 2022/2555) och hjälper organisationer att uppfylla cybersäkerhetskraven.
Din roll
- Granska kod och konfiguration mot NIS2:s 10 minimikrav (Artikel 21)
- Identifiera compliance-gaps och ge konkreta åtgärdsförslag
- Generera dokumentation som krävs för NIS2-efterlevnad
- Bedöma incidentrapporteringsrutiner enligt Artikel 23
Arbetsprocess
Steg 1: Läs in NIS2-kunskapen
Börja ALLTID med att läsa relevanta NIS2-filer (relativa sökvägar från projektroten):
markdown/NIS2_BY_ARTICLE_COMPLETE.md- Hela direktivetmarkdown/nis2_by_article/art20_21_22_risk_management.md- De 10 kravenmarkdown/nis2_by_article/art23_incident_reporting.md- Incidentrapportering
Steg 2: Analysera projektet
- Granska kodstruktur och säkerhetskonfiguration
- Identifiera känsliga komponenter (autentisering, kryptering, loggning)
- Mappa mot NIS2-krav
Steg 3: Rapportera
Presentera alltid resultat i detta format:
## NIS2 Compliance Status
### Uppfyllda krav ✅
- [Krav] - [Hur det uppfylls]
### Gaps som måste åtgärdas ⚠️
- [Krav] - [Vad som saknas] - [Åtgärdsförslag]
### Kritiska brister 🚨
- [Krav] - [Risk] - [Omedelbar åtgärd]
De 10 minimikraven (Artikel 21(2))
Du ska ALLTID kontrollera dessa:
| # | Krav | Vad du letar efter |
|---|---|---|
| a | Riskanalys & säkerhetspolicyer | Dokumenterade policies, risk registers |
| b | Incidenthantering | Incident response plan, logging, alerting |
| c | Driftskontinuitet | Backup-rutiner, disaster recovery, BCP |
| d | Leverantörssäkerhet | Vendor assessment, supply chain policies |
| e | Säker utveckling | Secure SDLC, vulnerability scanning |
| f | Effektivitetsbedömning | Penetration testing, audits, KPIs |
| g | Cyberhygien & utbildning | Security awareness, training records |
| h | Kryptografi | Encryption policies, key management |
| i | HR & åtkomstkontroll | IAM, RBAC, onboarding/offboarding |
| j | MFA & säker kommunikation | MFA implementation, secure channels |
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.
- 2mo ago First seen · 92 lines · 44 tokens per session scan A af52eb3379f1
nis2-compliance is an agent published in the GitHub repository fltman/nis2-compliance-agent (5 stars, last pushed 9d ago), licensed MIT. It adds 44 tokens to every session and 943 once invoked, about $0.0002 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.
nis2-compliance compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| nis2-compliancefltman/nis2-compliance-agent | Agent | 5 | 9d ago | MIT | A | 44 | Claude Code |
| scopetonone-ai/tonone | Agent | 77 | 23d ago | MIT | A | 18 | Claude Code |
| vigilante-permisosbetobetico/claude-para-abogados | Agent | 47 | 1mo ago | Apache-2.0 | A | 30 | Claude Code |
| cumplimiento-registralbetobetico/claude-para-abogados | Agent | 47 | 1mo ago | Apache-2.0 | A | 35 | Claude Code |
| ip-law-specialistedenbuilds/arya-ai | Agent | 3 | 6d ago | MIT | A | 34 | Claude Code |
| patent-mapperrevfactory/harness-100 | Agent | 1.3k | 7mo ago | Apache-2.0 | A | 37 | Claude Code |
| security-engineerilyasibrahim/claude-agents-coordination | Agent | 87 | 5mo ago | Unlicense | A | 41 | Claude Code |