security-documentation

security-documentation is a skill for Claude Code from spjoshis/claude-code-plugins. It costs 22 tokens per session (706 once invoked), scanned A, original, no licence file.

A security-documentation guide for writing security policies, incident-response plans, security procedures, and compliance records. Incident response is the process of handling and recovering from a security problem.

In plain words
What is it for?
Use it to create security policies, document procedures, prepare incident-response plans, and maintain compliance documentation.
Why use it?
It helps keep security responsibilities and response steps clear and documented. This makes it easier to act consistently during incidents and reviews.

Skill for Claude Code

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

Part of the security-analyst plugin — 4 skills shipped together

Good fit Use it to create security policies, document procedures, prepare incident-response plans, and maintain compliance documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spjoshis/claude-code-plugins/security-documentation
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 spjoshis/claude-code-plugins --skill security-documentation
Clone the repo
git clone --depth 1 https://github.com/spjoshis/claude-code-plugins

Made for: Claude Code.

Or install security-analyst, the plugin that ships this one along with the rest of its 4 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-documentation

README.md
[![agentmods](https://agentmods.dev/badge/skills/spjoshis/claude-code-plugins/security-documentation/github.svg)](https://agentmods.dev/skills/spjoshis/claude-code-plugins/security-documentation)
Your own site
<a href="https://agentmods.dev/skills/spjoshis/claude-code-plugins/security-documentation"><img src="https://agentmods.dev/badge/skills/spjoshis/claude-code-plugins/security-documentation/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-documentation

Your own site · 80×15
<a href="https://agentmods.dev/skills/spjoshis/claude-code-plugins/security-documentation"><img src="https://agentmods.dev/badge/skills/spjoshis/claude-code-plugins/security-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 706 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.00022 $0.00706
Opus 5.5 $0.00009 $0.00282
Sonnet 5.5 $0.00004 $0.00141
Haiku 4.5 $0.00002 $0.00071

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

Security

Grade A, and why

security-documentation 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.

plugins/security-analyst/skills/security-documentation/SKILL.md · 141 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

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. 1mo ago First seen · 141 lines · 22 tokens per session scan A 0e8c64934a3d

Subscribe to this mod's changes

security-documentation is a skill published in the GitHub repository spjoshis/claude-code-plugins (7 stars, last pushed 8mo ago), with no licence file. It adds 22 tokens to every session and 706 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

code-license-position

Check a vendor's licence FAQ and discussion threads before calling a LICENSE restriction a blocker. Use when a model or dependency licence seems to forbid use.

laurigates/claude-plugins · 33 tokens

governance

Manage openEHR specification governance: releases, change requests (CR/PR), versioning, and lifecycle states (Planning, Development, Trial, Stable, Paused, Retired). This skill should be used when the user asks to create, tag, or fix a release, update release entries in manifest.json, raise or progress a CR/PR…

openEHR/ai-plugins · 124 tokens

cease-desist

Draft a cease-and-desist letter (send mode) or triage one you received (receive mode). Use when asserting your rights against an infringer with a demand letter calibrated to your enforcement posture, or when an incoming C&D needs triage into a structured options memo with a recommendation.

uk-agents/uk-legal-plugins · 63 tokens

claim-chart

Build or review an element chart — a patent claim chart (infringement, invalidity, or review) or a civil element chart for any cause of action or defence — with every cell pin-cited and gap detection as the priority output. Use when the user asks for a claim chart, element chart, proof chart, infringement or…

uk-agents/uk-legal-plugins · 93 tokens

aia-generation

Run an AI impact assessment — structured intake, risk analysis, UK regulatory classification (UK GDPR / DPA 2018, ICO AI guidance, sector-specific UK regulation), EU AI Act analysis where EU nexus exists, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed…

uk-agents/uk-legal-plugins · 149 tokens

integration-management

Post-completion M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initialises from whatever deal artefacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A…

uk-agents/uk-legal-plugins · 103 tokens