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-business-continuity-plangit 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-business-continuity-plan)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-business-continuity-plan"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-business-continuity-plan/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-business-continuity-plan"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-business-continuity-plan.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.00059 | $0.01358 |
| Opus 5.5 | $0.00024 | $0.00543 |
| Sonnet 5.5 | $0.00012 | $0.00272 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
design-business-continuity-plan 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 Business Continuity Plan
Prepare the organization to keep its critical business functions running through a major disruption — a facility loss, a key-supplier failure, a pandemic, or another severe operational shock — covering the full range of people, processes, and facilities the organization depends on, not only its IT systems and data recovery, which a narrower disaster-recovery plan typically addresses.
Why This Is Best Practice
Adopted by: ISO 22301, "Security and Resilience — Business Continuity Management Systems," is the internationally recognized standard for organizational business continuity management, adopted and certified against by organizations across industries seeking to formalize their preparedness for disruptions that go beyond IT infrastructure alone. Impact: An organization with a well-developed IT disaster-recovery plan but no broader business continity plan can find its technology systems restored quickly after a disruption while still being unable to actually operate — because key personnel are unavailable, a critical physical facility is inaccessible, or an essential supplier relationship has failed — gaps a narrowly IT-focused plan doesn't address at all. Why best: Modern organizations depend on far more than their IT systems to function — physical facilities, specific personnel and their availability, supplier and partner relationships, and manual or semi-manual processes all represent points of failure a disruption can hit, and a business continuity plan addressing only IT systems leaves these other dependencies entirely unprepared for, even if the technology recovery itself is well executed.
Sources: ISO 22301:2019, "Security and Resilience — Business Continuity Management Systems — Requirements," International Organization for Standardization
Steps
Step 1: Identify critical business functions and their dependencies
Identify the organization's critical business functions — the activities that must continue or be restored quickly to avoid unacceptable damage — and map each function's actual dependencies: specific personnel, facilities, suppliers, technology systems, and processes it relies on.
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 · 59 tokens per session scan A 73723e07f488
design-business-continuity-plan is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 1,358 once invoked, about $0.0002 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.
research-first-development
Build knowledge bases that build software — research before code, teach before execute.
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.