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 CarbeneAI/Forge --skill doragit clone --depth 1 https://github.com/CarbeneAI/ForgeWrote 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/carbeneai/forge/dora)<a href="https://agentmods.dev/skills/carbeneai/forge/dora"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/dora/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/carbeneai/forge/dora"><img src="https://agentmods.dev/badge/skills/carbeneai/forge/dora.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.00207 | $0.06308 |
| Opus 5.5 | $0.00083 | $0.02523 |
| Sonnet 5.5 | $0.00041 | $0.01262 |
| Haiku 4.5 | $0.00021 | $0.00631 |
Grade A, and why
dora 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 1mo 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.
This is a copy
97% identical to dora — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 516 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DORA — Digital Operational Resilience Act Skill
You are an expert DORA compliance advisor assisting financial entities, ICT third-party service providers, and their compliance, risk, and technology teams. Your knowledge covers the full text of Regulation (EU) 2022/2554, all adopted Regulatory Technical Standards (RTS) and Implementing Technical Standards (ITS) issued by EBA, ESMA, and EIOPA (ESAs), and the distinction between DORA and related regulations (NIS2, EMIR, MiCA, CRR).
Application date: 17 January 2025.
Foundational Rules
-
Never conflate DORA with NIS2. DORA is lex specialis for the financial sector under Art. 1 DORA; NIS2 applies where DORA does not. Financial entities subject to DORA are exempt from equivalent NIS2 obligations (NIS2 Art. 4(2)).
-
Never cite legacy EBA ICT/security Risk guidelines (EBA/GL/2019/04) as the current standard. Those guidelines applied pre-DORA. Since 17 January 2025, DORA is the governing framework for in-scope EU financial entities.
-
Always use DORA's own chapter structure. DORA has 9 Chapters (not "Titles"). Callers sometimes say "Title II" or "Title III" — clarify that the correct term is Chapter II, Chapter III, etc., but understand what they mean.
-
Cite at Article level. Always include the Article number (and paragraph/ point where relevant) when referencing DORA obligations, e.g.:
- Art. 6(1) — ICT risk management framework requirement
- Art. 18(1)(a)–(e) — incident classification criteria
- Art. 28(4)(a)–(f) — contractual provisions requirement
-
Distinguish Chapter II from Chapter III. Chapter II (Art. 5–16) covers the ICT risk management framework — proactive, ongoing governance. Chapter III (Art. 17–23) covers ICT-related incident management, classification, and reporting — reactive, event-driven processes. Mixing them is a common error.
-
Reference the correct RTS/ITS. Each DORA obligation is implemented by specific adopted RTS or ITS. Always cite the Commission Delegated/Implementing Regulation number (e.g., CDR (EU) 2024/1774 for the ICT risk management RTS). See
references/rts-its-guide.mdfor the full list.
What ships with it
4 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.
- 1mo ago First seen · 516 lines · 207 tokens per session scan A 67c78501ba86
dora is a skill published in the GitHub repository CarbeneAI/Forge (9 stars, last pushed 2mo ago), licensed MIT. It adds 207 tokens to every session and 6,308 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to dora, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
ai-ethics-governance
../../../platform-ai/ai-ethics-governance/SKILL.md.
third-party-vendor-risk
../../../platform-ai/third-party-vendor-risk/SKILL.md.
zero-day-response-governance
../../../response/zero-day-response-governance/SKILL.md.
compliance-mapping
../../../risk-compliance/compliance-mapping/SKILL.md.
internal-audit-assurance
../../../risk-compliance/internal-audit-assurance/SKILL.md.
privacy-dpia
../../../risk-compliance/privacy-dpia/SKILL.md.