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 daddia/claude-for-strategy --skill raid-loggit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/raid-log)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/raid-log"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/raid-log/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/daddia/claude-for-strategy/raid-log"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/raid-log.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.00054 | $0.00783 |
| Opus 5.5 | $0.00022 | $0.00313 |
| Sonnet 5.5 | $0.00011 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
raid-log 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RAID Log
When to use
Append/update persisted RAID log using profile definitions and severity scale — escalation threshold enforced.
What this skill does not do
- Does not downgrade severity to avoid escalation — severity laundering guarded.
- Does not leave entries unowned.
- Does not output only new row — full updated log for save-back.
Preconditions
| Input | If missing |
|---|---|
| Entry to log (description) | Ask |
| Current RAID log | Create new if none; use profile format |
| Practice profile (RAID definitions, severity, escalation) | Sensible default; [PROVISIONAL] |
Provisional mode
Ambiguous Risk vs Assumption: ask using profile definitions — don't guess.
Trust spine
- Confidence bands (
governance-tracking):- High: Classified, severity with rationale, owner assigned, escalation flagged if threshold met.
- Medium: Classification confirmed with user.
- Low: Severity without rationale — require one-line rationale.
- Failure modes:
- Incentive Gaming: Guards severity laundering — downgrading risks to assumptions or softening language.
- Escalation triggers: Entry meets profile threshold — ESCALATION FLAG explicit, not deferred.
Workflow
- Read profile for RAID format, definitions, severity scale.
- Get current log.
- Classify entry — ask if ambiguous.
- Assign severity with one-line rationale.
- Assign owner.
- Check escalation threshold.
- Output full updated log + ESCALATION FLAG if applicable.
- Gaming-pattern check before output.
Output format
CONFIDENCE: [defensible recommendation | structured first pass]
[Full RAID log table]
ESCALATION FLAG: [if threshold met — why]
Worked example
Input: "Vendor may slip delivery" logged as Assumption, severity Low, no owner.
Expected output: Reclassify as Risk [review]; severity rationale required; owner assigned; escalation assessed.
Quality checks before delivering
- Profile definitions used for classification
- Severity has rationale
- Owner assigned
- Full log output
- Escalation flag when threshold met
- Gaming-pattern check run
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.
- 1mo ago First seen · 95 lines · 54 tokens per session scan A e91fa82e5db7
raid-log is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 783 once invoked, about $0.0002 per session on Opus 5.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
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.
to-spec
Turn the settled conversation into a spec (PRD), published through the repo's tracker: .specs/specs/ .md by default.
setup
Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the default).
meeting-notes-to-tasks
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
loom-usage
Meta-orchestration skill for Claude driving loom itself.
task-decomposition
Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.