design-policy-management-lifecycle

design-policy-management-lifecycle is a skill for Claude Code from jeffreytse/grimoire-core. It costs 66 tokens per session (1,237 once invoked), scanned A, original, MIT.

A process for creating, approving, reviewing, updating, and retiring an organization's policies. It gives each policy an owner, a review schedule, and one official place to store it.

In plain words
What is it for?
Use it to set up policy ownership, approval steps, scheduled reviews, version control, and policy retirement.
Why use it?
It prevents outdated, conflicting, or forgotten policies from remaining in use. Everyone can find the current approved version and know when it needs review.

Skill for Claude Code

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

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

Good fit Use it to set up policy ownership, approval steps, scheduled reviews, version control, and policy retirement.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/design-policy-management-lifecycle
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-policy-management-lifecycle
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 145 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-policy-management-lifecycle

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-policy-management-lifecycle"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-policy-management-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,237 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.00066 $0.01237
Opus 5 $0.00033 $0.00619
Sonnet 5 $0.00013 $0.00247
Haiku 4.5 $0.00007 $0.00124

Measured 9d ago against content hash e6d48882fd2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

design-policy-management-lifecycle 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.

skills/business/operations/skills/design-policy-management-lifecycle/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 Policy Management Lifecycle

Establish a formal policy lifecycle — with an accountable owner for each policy, a defined review cadence, and a single authoritative repository — rather than letting policies proliferate as scattered documents with no owner and no scheduled review.

Why This Is Best Practice

Adopted by: ISO 9001:2015's documented information control requirements establish formal expectations for creating, reviewing, approving, and maintaining organizational policy documents as part of a certified quality management system, and formal policy lifecycle management is standard practice across organizations maintaining ISO certification or similar structured governance requirements. Impact: Organizations without a formal policy lifecycle are documented to accumulate outdated, contradictory, or unowned policies over time — a policy written years ago by someone no longer at the company, referencing a process that no longer exists, sitting alongside a newer policy that contradicts it — because no defined process exists for retiring or updating policies as circumstances change. Why best: A policy created once and never revisited tends to become stale as the organization and its circumstances evolve, and without a defined owner, no one is specifically responsible for noticing this staleness or updating the policy — a formal lifecycle with assigned ownership and a scheduled review cadence is what actually keeps policies current rather than allowing them to silently drift out of relevance.

Sources: International Organization for Standardization, ISO 9001:2015, "Quality Management Systems — Requirements," documented information control clauses

Steps

Step 1: Establish a single authoritative policy repository

Establish a single, authoritative repository where all official organizational policies live, so that employees and managers have one place to find the current, correct version of any policy — rather than scattered, potentially conflicting versions living in different documents, folders, or communication channels.

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. 9d ago First seen · 68 lines · 66 tokens per session scan A e6d48882fd2f

Subscribe to this mod's changes

design-policy-management-lifecycle is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 23d ago), licensed MIT. It adds 66 tokens to every session and 1,237 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-09-03.