security-change-rollout-planning

security-change-rollout-planning is a skill for Claude Code from bookforge-ai/bookforge-skills. It costs 188 tokens per session (6,056 once invoked), scanned A, original, CC-BY-SA-4.0.

A planning guide for introducing security changes across a service or a group of systems. It covers timing, risk levels, gradual releases, and communication.

In plain words
What is it for?
Use it to plan short-, medium-, or long-term security work, rank affected systems by risk, release changes gradually, and prepare internal or external messages.
Why use it?
It reduces the chance that a security fix will cause a widespread outage or leave important systems unprotected. It also clarifies who needs to know about the change and when.

Skill for Claude Code

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

Part of the building-secure-and-reliable-systems plugin — 14 skills shipped together

Good fit Use it to plan short-, medium-, or long-term security work, rank affected systems by risk, release changes gradually, and prepare internal or external messages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bookforge-ai/bookforge-skills/security-change-rollout-planning
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 bookforge-ai/bookforge-skills --skill security-change-rollout-planning
Clone the repo
git clone --depth 1 https://github.com/bookforge-ai/bookforge-skills

Made for: Claude Code.

Or install building-secure-and-reliable-systems, the plugin that ships this one along with the rest of its 14 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 security-change-rollout-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/bookforge-ai/bookforge-skills/security-change-rollout-planning/github.svg)](https://agentmods.dev/skills/bookforge-ai/bookforge-skills/security-change-rollout-planning)
Your own site
<a href="https://agentmods.dev/skills/bookforge-ai/bookforge-skills/security-change-rollout-planning"><img src="https://agentmods.dev/badge/skills/bookforge-ai/bookforge-skills/security-change-rollout-planning/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 security-change-rollout-planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/bookforge-ai/bookforge-skills/security-change-rollout-planning"><img src="https://agentmods.dev/badge/skills/bookforge-ai/bookforge-skills/security-change-rollout-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 188 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,056 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 unknown 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.00188 $0.06056
Opus 5 $0.00094 $0.03028
Sonnet 5 $0.00038 $0.01211
Haiku 4.5 $0.00019 $0.00606

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

Security

Grade A, and why

security-change-rollout-planning 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.

books/building-secure-and-reliable-systems/skills/security-change-rollout-planning/SKILL.md · 359 lines

The source is not reproduced here

Licensed CC-BY-SA-4.0

The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 11d ago First seen · 359 lines · 188 tokens per session scan A 1d2601cf6f15

Subscribe to this mod's changes

security-change-rollout-planning is a skill published in the GitHub repository bookforge-ai/bookforge-skills (35 stars, last pushed 4mo ago), licensed CC-BY-SA-4.0. It adds 188 tokens to every session and 6,056 once invoked, about $0.0009 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-30.

Related

Other skills, from other repositories

k8s-incident-triage

Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.

initializ/forge · 41 tokens

design-incident-response

Use when creating or improving an incident response process for a production system or operational team.

jeffreytse/grimoire-core · 21 tokens

Incident Response Planner

Analyze an infrastructure incident alert and produce a structured response plan plus an executable on-call runbook. Use for incident, alert, on-call, and runbook requests.

AgentEra/Agently · 37 tokens

building-ransomware-playbook-with-cisa-framework

Builds a structured ransomware incident response playbook aligned with the CISA StopRansomware Guide and NIST Cybersecurity Framework. Covers preparation, detection, containment, eradication, recovery, and post-incident phases with actionable checklists. Activates for requests involving ransomware response planning…

26zl/cybersec-toolkit · 83 tokens

sre-expert

Expert-level site reliability engineering, SLOs, incident management, and operational excellence. Use when the user mentions reliability, monitoring, incident management, SLOs, or observability, or when the task involves SRE Fundamentals, Reliability Practices, SRE Principles, or On-Call.

personamanagmentlayer/pcl · 63 tokens

cybersecurity-expert

Build comprehensive cybersecurity solutions including threat detection, incident response, vulnerability management, and security compliance monitoring. Use when the user mentions threat detection, SIEM, incident response, vulnerability management, security monitoring, or security compliance programs.

personamanagmentlayer/pcl · 50 tokens