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 Dokkabei97/forged-claude-code --skill risk-registergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/risk-register)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/risk-register"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/risk-register.svg" alt="Measured on agentmods" 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.00027 | $0.00806 |
| Opus 5 | $0.00014 | $0.00403 |
| Sonnet 5 | $0.00005 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
risk-register 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 7d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Risk Register - Startup Risk Management
Overview
Identifies, assesses, and tracks risks before they become crises. Startups that manage risk proactively survive longer.
1. When to Apply
| Trigger | Behavior |
|---|---|
| Quarterly review | Full risk assessment |
| "risk", "리스크" | Risk register creation/update |
| Major decision | Decision-specific risk analysis |
| Incident occurred | Add to risk register with lessons |
2. Risk Register Template
# Risk Register — [Date]
| ID | Risk | Category | Probability | Impact | Score | Owner | Status |
|----|------|----------|-------------|--------|-------|-------|--------|
| R1 | [Description] | [Cat] | H/M/L | H/M/L | [N] | @name | Open |
| R2 | [Description] | [Cat] | H/M/L | H/M/L | [N] | @name | Mitigated |
## Risk Detail: R1 — [Risk Name]
- **Description**: [What could go wrong]
- **Trigger**: [What would cause this to happen]
- **Probability**: High (>70%) / Medium (30-70%) / Low (<30%)
- **Impact**: High (existential) / Medium (significant) / Low (manageable)
- **Mitigation Plan**: [What we're doing to reduce probability/impact]
- **Contingency Plan**: [What we'll do IF it happens]
- **Owner**: @[name]
- **Review Date**: [When to reassess]
3. Common Startup Risks
| Category | Risk | Typical Probability |
|---|---|---|
| Financial | Runway runs out before next raise | High |
| Financial | Key customer churns | Medium |
| Technical | Major security breach | Low but catastrophic |
| Technical | Key infrastructure failure | Medium |
| People | Co-founder departure | Medium |
| People | Key engineer leaves | Medium |
| Market | Competitor launches similar product | High |
| Market | Market shifts (regulation, trends) | Medium |
| Legal | IP dispute | Low |
| Legal | Compliance violation | Medium |
| Operational | Vendor/partner dependency fails | Medium |
4. Risk Matrix
Impact → Low Medium High
Probability
High | 🟡 Medium | 🟠 High | 🔴 Critical |
Medium | 🟢 Low | 🟡 Medium | 🟠 High |
Low | 🟢 Low | 🟢 Low | 🟡 Medium |
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.
- 7d ago First seen · 113 lines · 27 tokens per session scan A 15d3f4c18bc1
risk-register is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 806 once invoked, about $0.0001 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
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.
vellum-skills-catalog
Discover bundled skills and search/install community skills from the skills.sh registry.