What is security-status-report?

A workflow that creates a security status report by evaluating threats listed in a project’s docs/threats.json file with separate AI agents.

Use it to generate the required agent tasks, run them concurrently, and collect their results into a security status report.

It turns a threat list into scored security findings through a repeatable process instead of requiring a manual assessment of every threat.

security-status-report — Skill by agent-substrate

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.

agentmods

npx agentmods add skills/agent-substrate/substrate/security-status-report

Any agent

npx skills add agent-substrate/substrate --skill security-status-report

Clone the repo

git clone --depth 1 https://github.com/agent-substrate/substrate

Made for: Claude Code, Codex.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 427 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00032	$0.00427
Opus 5	$0.00016	$0.00214
Sonnet 5	$0.00006	$0.00085
Haiku 4.5	$0.00003	$0.00043

Measured 2d ago against content hash 440865021b33, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security-status-report 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 2d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/compile_report.py, scripts/render_chart.py, scripts/template_dispatch.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/security-status-report/SKILL.md · 21 lines

What it actually says

Task

Generate a security status report by evaluating threats listed in docs/threats.json.

Workflow

Copy .agents/skills/security-status-report/scripts/template_dispatch.py to .agents/scratch/security-status-report/template_dispatch.py.
Complete the TODO in .agents/scratch/security-status-report/template_dispatch.py, meeting the following requirements: a. Iterate over each threat from docs/threats.json to produce a list of invocations that matches your tool for invoking sub-agents. b. Each invocation must address a single threat, use the below prompt, and instruct the sub-agent to output the correct schema.
Execute the script from the repository root, specifying .agents/scratch/security-status-report/subagents.json as the output file argument (python3 .agents/scratch/security-status-report/template_dispatch.py .agents/scratch/security-status-report/subagents.json).
Read .agents/scratch/security-status-report/subagents.json and copy its exact JSON array into your tool for invoking subagents. DO NOT manually craft or bypass the invocations. Run ALL generated sub-agents concurrently in a single tool call by default unless bound by model rate limits or harness concurrency limits (use batching intelligently if needed). You already updated the script in step 2 to output exactly what you need, so no modifications to the output should be necessary unless you made a mistake or hit limits.
Wait for all sub-agents to complete.
Run python3 .agents/skills/security-status-report/scripts/compile_report.py docs/threats.json .agents/scratch/security-status-report .agents/scratch/security-status-report/final.json to produce the final report.
Run python3 .agents/skills/security-status-report/scripts/render_chart.py .agents/scratch/security-status-report/final.json .agents/scratch/security-status-report/chart.png to render a bar chart of the scores.

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago First seen · 21 lines · 32 tokens per session scan A 440865021b33

Subscribe to this mod's changes

security-status-report is a skill published in the GitHub repository agent-substrate/substrate (1,703 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 427 once invoked, about $0.0002 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.

Security

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens