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 taivop/marketplace --skill cyber-incidents-cert-eegit clone --depth 1 https://github.com/taivop/marketplaceWrote 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/taivop/marketplace/cyber-incidents-cert-ee)<a href="https://agentmods.dev/skills/taivop/marketplace/cyber-incidents-cert-ee"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/cyber-incidents-cert-ee/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/taivop/marketplace/cyber-incidents-cert-ee"><img src="https://agentmods.dev/badge/skills/taivop/marketplace/cyber-incidents-cert-ee.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.00037 | $0.00399 |
| Opus 5 | $0.00018 | $0.00199 |
| Sonnet 5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
cyber-incidents-cert-ee 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.
What it actually says
RIA Cyber-Situation Reports
Access
- Publication index:
https://www.ria.ee/en/cyber-security/cyberspace-analysis-and-prevention/situation-cyberspace - Public server-rendered HTML linking report pages and PDFs; no login or JavaScript is required.
Retrieve
The index groups publications into:
- monthly summaries from 2023 onward
- quarterly assessments through 2023
- annual
Cyber Security in Estoniareports
Select the period first. Resolve relative monthly report and /sites/default/files/documents/...pdf links against https://www.ria.ee. Newer monthly entries may be HTML articles while older entries are PDFs.
Extract incident totals, handled/impactful incident distinctions, phishing/malware/DDoS and availability categories, significant events, comparison period, and any revised definitions. Use the annual reports for yearly totals and methodology; use monthly reports for timely operational context.
Return
- Preserve report period, publication date, metric label, count/rate, comparison value, definition, source URL, page/section, and retrieval time.
- Keep observed incidents separate from reports received, incidents handled, vulnerabilities, and automated monitoring events.
- Quote category labels exactly before adding normalized categories.
Limits
- Public reports are curated aggregates, not the confidential CERT-EE incident database.
- Publication format varies between HTML and PDF across years.
- The former incident-handling landing page describes CERT-EE procedures but does not itself provide incident records.
Verify
- Require the index to expose multiple monthly years, monthly report links, quarterly assessments, and annual cyber-security reports.
- Require selected PDF files to begin
%PDF-; for HTML reports, require the requested month/year and incident-related content.
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 · 41 lines · 37 tokens per session scan A 898c7d6d3bb6
cyber-incidents-cert-ee is a skill published in the GitHub repository taivop/marketplace (17 stars, last pushed 12d ago), licensed MIT. It adds 37 tokens to every session and 399 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…