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 design-decision-rightsgit 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/design-decision-rights)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/design-decision-rights"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/design-decision-rights/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/design-decision-rights"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/design-decision-rights.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.00053 | $0.00970 |
| Opus 5 | $0.00026 | $0.00485 |
| Sonnet 5 | $0.00011 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
design-decision-rights 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 11d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Decision Rights
When to use
Assign RACI/RAPID roles with exactly one Accountable per decision — enforce single-point accountability and flag Consulted bloat.
What this skill does not do
- Does not diagnose structure fit — route to
/operating-model:diagnose-structure-fit. - Does not resolve political ownership — forces a choice; strategist decides.
- Does not implement governance systems — produces artifact for adoption.
Preconditions
| Input | If missing |
|---|---|
| Decisions or processes in scope | Ask user to list |
| Practice profile (RACI vs RAPID convention) | Default RACI; flag [PROVISIONAL] |
| Named roles/parties for assignment | Ask; halt if decisions unnamed |
Provisional mode
Multiple Accountable proposed: flag diffused accountability; do not finalize until single owner chosen or explicitly [review].
Trust spine
- Confidence bands (
structured-aggregation):- High: Every decision has exactly one Accountable; bloat flags applied.
- Medium: Some ownership gaps with recommended owners.
- Low: Zero Accountable on key decisions — halt output until resolved.
- Failure modes:
- Strategic advice vs. support: Assignments are draft for exec confirmation.
- Client confidentiality: RACI may expose sensitive authority lines — CONFIDENTIAL header.
- Accountability gap: "Shared ownership" rejected; forces single Accountable.
- Analytical Rigor: MECE decision coverage in scope.
- Incentive Gaming: Consulted bloat flagged as latency/gaming risk.
- Escalation triggers: Unowned decisions found — name specifically, do not defer.
Workflow
- Read practice profile for decision-rights gaps and house convention.
- Assign roles per decision — R/A/C/I or RAPID equivalent.
- Enforce exactly one Accountable — stop if zero; flag if multiple.
- Check Consulted bloat — long lists that slow decisions materially.
- Find unowned decisions — no claimed owner during exercise.
- Completeness check before output.
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.
- 11d ago First seen · 107 lines · 53 tokens per session scan A 36b37cc8eb1d
design-decision-rights is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 970 once invoked, about $0.0003 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
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
nx-monorepo
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx.