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 jeffreytse/grimoire-core --skill design-decision-rights-frameworkgit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/design-decision-rights-framework)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-decision-rights-framework"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-decision-rights-framework/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/jeffreytse/grimoire-core/design-decision-rights-framework"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-decision-rights-framework.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.00070 | $0.01380 |
| Opus 5.5 | $0.00028 | $0.00552 |
| Sonnet 5.5 | $0.00014 | $0.00276 |
| Haiku 4.5 | $0.00007 | $0.00138 |
Grade A, and why
design-decision-rights-framework 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Decision Rights Framework
Explicitly map decision types to the specific role or body with final decision authority, distinct from who merely provides input — rather than leaving decision authority ambiguous and re-litigated each time a similar decision arises.
Why This Is Best Practice
Adopted by: Bain & Company's RAPID framework (Recommend, Agree, Perform, Input, Decide), introduced in Rogers & Blenko's "Who Has the D?" (Harvard Business Review, 2006), is one of the most widely adopted decision-rights frameworks in corporate strategy and organizational design practice, used to clarify decision authority across large, complex organizations where ambiguous authority repeatedly slows decision-making. Impact: Bain's own research documents that decision effectiveness (the speed and quality of organizational decision-making) correlates more strongly with clarity of decision rights than with almost any other organizational design factor studied — organizations with clear decision rights make faster, more consistently executed decisions than organizations with equivalent talent but ambiguous decision authority. Why best: Ambiguous decision authority means every decision of a given type gets re-litigated from scratch — who actually has the final call is negotiated anew each time rather than settled once, producing slower decisions and, worse, decisions that get revisited after the fact because the people who felt entitled to a say weren't clearly excluded from final authority in advance.
Sources: Rogers & Blenko, "Who Has the D? How Clear Decision Roles Enhance Organizational Performance," Harvard Business Review (2006); Bain & Company, RAPID decision-making framework
Steps
Step 1: Identify the recurring decision types causing friction
Identify the specific categories of decisions that recur and currently experience friction, delay, or repeated re-litigation — pricing decisions, hiring above a certain level, product feature prioritization — rather than attempting to map decision rights for every conceivable one-off decision the organization might face.
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 · 68 lines · 70 tokens per session scan A d8a7382628cf
design-decision-rights-framework is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 70 tokens to every session and 1,380 once invoked, about $0.0003 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
semantic-model-disambiguation
Analyze Power BI semantic models for column-level overlaps that confuse Copilot and Fabric data agents. Detect ambiguity, review with domain expert, apply fixes via MCP.
prompt-2-data
Generate comprehensive synthetic relational data for any specified subject with multiple normalized CSV files maintaining referential integrity.
academic-paper-drafting
End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies.
infrastructure-as-code
Domain: DevOps & Cloud Engineering.
agent-governance
Patterns for adding safety, trust, and policy enforcement to AI agent systems -- control which tools agents can call, what content they process, and maintain accountability through audit trails.
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…