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 pantheon-org/tekhne --skill risk-registergit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/risk-register)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/risk-register"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/risk-register/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/pantheon-org/tekhne/risk-register"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/risk-register.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 40 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00167 | $0.03224 |
| Opus 5 | $0.00084 | $0.01612 |
| Sonnet 5 | $0.00033 | $0.00645 |
| Haiku 4.5 | $0.00017 | $0.00322 |
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 9d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Risk Register
A single committed table (docs/RISK_REGISTER.md) of every deferred item, interim shortcut, and open architecture
decision that could otherwise get forgotten between sessions or team members. Unlike gitignored, session-local
scratch notes, this is a durable, shared, GitHub-visible record -- the register is the index; a scratch note or a PR
is where the extra detail lives, if there is more to say than fits in a row.
Prerequisites
docs/RISK_REGISTER.mdexists. If this is the first entry in a project and the file doesn't exist yet, create it with a# Risk Registertitle, an intro paragraph (paraphrase the one above), and an empty table using the columns inassets/templates/risk-register-row-template.yaml.assets/templates/risk-register-row-template.yaml-- the shape of a single row, illustratedassets/schemas/risk-register-row.schema.json-- the same shape, as enforceable constraintsscripts/validate-risk-register-append-only.shandscripts/validate-risk-register-schema.sh, both wired into a local pre-commit hook so a row can never silently vanish, and a malformed row can never be committed
When to Use
- The moment a shortcut is taken, a decision is postponed, or a known gap is discovered -- not retroactively.
- A scratch note is created for something that should also be durably tracked (most of them should; see Relationship to Sibling Conventions).
- Someone asks what's deferred, what's an accepted risk, or what's still open.
- An entry is actually resolved and needs to be marked as such.
When NOT to Use
- A finalized, accepted architectural decision with no open question -- that's an ADR (
adr-capture), not a risk. - Ephemeral, single-session scratch notes that don't need to outlive the current conversation -- no register entry needed.
- Anything confidential -- this file is committed and visible to everyone with repo access.
Row Schema
What ships with it
17 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.
- assets/schemas/risk-register-row.schema.json 2.2 KB
- assets/templates/risk-register-row-template.yaml 1.0 KB
- evals/instructions.json 3.2 KB
- evals/scenario-1/capability.txt 143 B
- evals/scenario-1/criteria.json 1.7 KB
- evals/scenario-1/task.md 2.5 KB
- evals/scenario-2/capability.txt 149 B
- evals/scenario-2/criteria.json 1.3 KB
- evals/scenario-2/task.md 1.9 KB
- evals/scenario-3/capability.txt 138 B
- evals/scenario-3/criteria.json 1.3 KB
- evals/scenario-3/task.md 2.1 KB
- evals/summary.json 127 B
- references/relationship-to-sibling-conventions.md 2.0 KB
- references/unresolved-verification-case-study.md 1.8 KB
- scripts/validate-risk-register-append-only.sh 2.0 KB runs code
- scripts/validate-risk-register-schema.sh 7.4 KB runs code
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.
- 9d ago First seen · 194 lines · 167 tokens per session scan A 8cbf27a8bc19
risk-register is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 167 tokens to every session and 3,224 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
template-instantiation
Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
turborepo-monorepo
Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance…
handover-admin
Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Use when handing over admin responsibilities, onboarding a new site administrator, or documenting admin procedures — e.g., "admin guide", "admin documentation", "admin handover".
Product Strategy
A comprehensive skill for product strategy — covering frameworks, opportunity sizing, prioritization, roadmap building, OKRs, and stakeholder management. From early-stage discovery to mature product org execution.