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 agentmods add skills/saolalab/clawforce/risk-assessmentnpx skills add saolalab/clawforce --skill risk-assessmentgit clone --depth 1 https://github.com/saolalab/clawforceWrote 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/saolalab/clawforce/risk-assessment)<a href="https://agentmods.dev/skills/saolalab/clawforce/risk-assessment"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/risk-assessment.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.00032 | $0.01996 |
| Opus 5 | $0.00016 | $0.00998 |
| Sonnet 5 | $0.00006 | $0.00399 |
| Haiku 4.5 | $0.00003 | $0.00200 |
Grade A, and why
risk-assessment 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 5d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Risk Assessment
This skill provides frameworks for identifying, assessing, and managing legal risks.
Risk Register Template
# Legal Risk Register
| ID | Risk Description | Category | Likelihood | Impact | Risk Score | Status | Owner | Mitigation Strategy | Next Review |
|----|------------------|----------|------------|--------|------------|--------|-------|---------------------|-------------|
| LR-001 | [Risk description] | [Contract/IP/Compliance/etc.] | [Low/Med/High] | [Low/Med/High] | [1-9] | [Open/Mitigated/Closed] | [Name] | [Strategy] | [Date] |
Risk Categories
- Contract: Contract-related risks (unfavorable terms, breach risk)
- IP: Intellectual property risks (infringement, misappropriation)
- Compliance: Regulatory compliance risks (GDPR, employment law)
- Litigation: Dispute and litigation risks
- Employment: Employment law risks (wrongful termination, discrimination)
- Data: Data protection and privacy risks
- Corporate: Corporate governance risks
Risk Scoring Matrix
Likelihood:
- Low (1): Unlikely to occur (< 10% probability)
- Medium (2): Possible to occur (10-50% probability)
- High (3): Likely to occur (> 50% probability)
Impact:
- Low (1): Minimal impact (minor financial loss, no operational impact)
- Medium (2): Moderate impact (significant financial loss, some operational impact)
- High (3): Severe impact (major financial loss, significant operational impact, reputational damage)
Risk Score = Likelihood × Impact
- 1-2: Low Risk — Accept or monitor
- 3-4: Medium Risk — Mitigate or transfer
- 6-9: High Risk — Mitigate immediately or avoid
Risk Response Strategies
- Accept: Risk is acceptable, no action needed
- Mitigate: Implement controls to reduce likelihood or impact
- Transfer: Use insurance, indemnification, or contracts to transfer risk
- Avoid: Eliminate the risk by changing approach or declining opportunity
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.
- 5d ago First seen · 227 lines · 32 tokens per session scan A dea8d48801ff
risk-assessment is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 1,996 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
jp-compliance-reporter
Generate regulatory compliance reports for Japanese financial institutions.
ai-act-readiness
../../../compliance-os/skills/ai-act-readiness/SKILL.md.
contract-and-proposal-writer
../../../business-growth/skills/contract-and-proposal-writer/SKILL.md.
capa-officer
../../../ra-qm-team/skills/capa-officer/SKILL.md.
compliance-os-bundle
../../../compliance-os/skills/compliance-os/SKILL.md.
arxiv-summarizer-orchestrator
End-to-end orchestration skill for periodic arXiv collection and reporting using three sub-skills: arxiv-search-collector, arxiv-paper-processor, and arxiv-batch-reporter. Supports manual language control across all markdown outputs and Stage-B processing strategy (subagentparallel default max 5, or serial).