design-conflict-of-interest-policy

design-conflict-of-interest-policy is a skill for Claude Code from jeffreytse/grimoire-core. It costs 70 tokens per session (1,322 once invoked), scanned A, original, MIT.

A standing policy requiring employees, officers, and board members to disclose personal, financial, or relationship interests that could conflict with their duties. It also defines when someone must step out of a decision, known as recusal.

In plain words
What is it for?
Creating periodic disclosure requirements, reviewing reported conflicts, and defining how conflicted people are excluded from decisions.
Why use it?
Relying on people to mention conflicts only when they remember can leave important conflicts undisclosed and undermine fair decisions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 156 skills shipped together

Good fit Creating periodic disclosure requirements, reviewing reported conflicts, and defining how conflicted people are excluded from decisions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/design-conflict-of-interest-policy
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill design-conflict-of-interest-policy
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 156 skills.

Wrote 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.

agentmods badge for design-conflict-of-interest-policy

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-conflict-of-interest-policy/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/design-conflict-of-interest-policy)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-conflict-of-interest-policy"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-conflict-of-interest-policy/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.

agentmods 80×15 button for design-conflict-of-interest-policy

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-conflict-of-interest-policy"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-conflict-of-interest-policy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,322 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.01322
Opus 5.5 $0.00028 $0.00529
Sonnet 5.5 $0.00014 $0.00264
Haiku 4.5 $0.00007 $0.00132

Measured 1mo ago against content hash 2c3801e60ce4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-conflict-of-interest-policy 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.

skills/business/operations/skills/design-conflict-of-interest-policy/SKILL.md · 68 lines

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 Conflict-of-Interest Policy

Establish a standing policy requiring employees, officers, and board members to proactively and periodically disclose personal, financial, or relational interests that could conflict with their organizational duties, with a defined recusal process for identified conflicts — rather than relying on individuals to voluntarily raise conflicts only when they happen to think of it.

Why This Is Best Practice

Adopted by: The COSO Internal Control — Integrated Framework identifies conflict-of-interest management as a core component of an effective internal control environment, and standing conflict-of-interest disclosure policies with periodic mandatory disclosure are standard governance practice across corporations and nonprofits, commonly required as a condition of tax-exempt status determinations and institutional grant eligibility for nonprofit organizations. Impact: Organizations relying on voluntary, as-needed conflict disclosure are documented to catch conflicts far less reliably than organizations with mandatory, periodic disclosure requirements, since an individual with an undisclosed conflict has limited incentive to proactively raise it, and even well-intentioned individuals can fail to recognize a conflict without a structured prompt requiring them to actively consider and disclose specific categories of relationship. Why best: Waiting for an individual to voluntarily recognize and disclose a conflict places the entire burden of catching the conflict on the person with the least incentive to surface it — a mandatory, periodic disclosure process instead structurally prompts every covered individual to actively consider and report specific categories of potential conflict on a defined schedule, catching conflicts that ad hoc, voluntary disclosure would likely miss.

Sources: Committee of Sponsoring Organizations of the Treadway Commission (COSO), Internal Control — Integrated Framework; standard nonprofit and corporate governance conflict-of-interest disclosure practice

Read the full file on GitHub · 68 lines

Changes

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.

  1. 1mo ago First seen · 68 lines · 70 tokens per session scan A 2c3801e60ce4

Subscribe to this mod's changes

design-conflict-of-interest-policy 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,322 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.