Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/andreaswasita/copilot-agents-dojonpx agentmods add skills/andreaswasita/copilot-agents-dojo/derive-security-from-riskWrote 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/andreaswasita/copilot-agents-dojo/derive-security-from-risk)<a href="https://agentmods.dev/skills/andreaswasita/copilot-agents-dojo/derive-security-from-risk"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/derive-security-from-risk/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/andreaswasita/copilot-agents-dojo/derive-security-from-risk"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/derive-security-from-risk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.01272 |
| Opus 5 | $0.00007 | $0.00636 |
| Sonnet 5 | $0.00003 | $0.00254 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
derive-security-from-risk 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.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Derive Security From Risk
Turns a ratified business driver or functional requirement — together with a named threat — into a Security Requirement (SR) the gate can verify. This skill does NOT propose generic controls and does NOT parent SRs to unspecified parent risks; every SR names the obligation or threat it satisfies.
When to Use
- A
BR-*orFR-*exists for the engagement and processes regulated data, money, identity, or controlled access. - A threat modelling session (STRIDE, LINDDUN, attack tree) has produced a concrete threat the architecture must mitigate.
- A compliance obligation (PCI, HIPAA, APRA CPS 234, GDPR, ISO 27001 Annex A) maps to a control the design must enforce.
- NOT when nobody can name the threat yet — run a threat-modelling session first; do not derive a control to look productive.
Prerequisites
- The parent
BR-*orFR-*exists inrequirements/<engagement>/and is ratified. - A named threat or obligation is recorded in
requirements/<engagement>/threats/<threat-id>.md(free-form, but the SR body must cite it). spec/artifact-schema.mdis the contract for SR frontmatter.
If no named threat exists, stop. The TOGAF red thread breaks the moment a control mitigates a threat nobody named.
How to Run
bash scripts/verify-traceability.sh requirements/<engagement>
# create requirements/<engagement>/SR/SR-NNN.md
bash scripts/verify-traceability.sh requirements/<engagement>
Quick Reference
| Action | Tool | Notes |
|---|---|---|
| Read parent BR/FR | view |
Get exact id. |
| Read threat record | view |
The threat ID goes in the SR body. |
| Write SR | create |
Frontmatter per schema; measurable: true. |
| Verify lineage | bash scripts/verify-traceability.sh |
Must pass before commit. |
Example SR frontmatter:
---
id: SR-003
layer: SR
title: PII masking before persistence
parent_ids: [BR-001, FR-002]
owner: [email protected]
measurable: true
ratified_by: ""
target: "Zero unmasked PII fields in storage; verified by daily DLP scan."
derivation_skill: derive-security-from-risk
tags: [pii, masking, data-protection, threat-T03]
---
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 · 144 lines · 14 tokens per session scan A 996fa595e15e
derive-security-from-risk is a skill published in the GitHub repository andreaswasita/copilot-agents-dojo (53 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 1,272 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-30.
Other skills, from other repositories
decision-ledger
A session record for tracking unresolved decisions and drafting them into `.governance/claims/` when they are settled. It preserves both the decision and the reason behind it.
governance-bootstrap
A guided checklist for creating a project's governance system from scratch when no governance exists.
session-grounding
A session-start procedure for checking the current facts, scope, and work track in a governed project before taking action.
truth-first
A set of rules for writing technical conclusions and performing irreversible or state-changing operations. It requires evidence tied to file and line locations and restricts unsupported claims.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.