Claude Statusbar
leeguooooo/claude-code-usage-bar
Manage cs (claude-statusbar) — switch theme/style/density, override severity colors, preview combinations, run doctor, reset config, install, upgrade (cs upgrade — the only supported upgrade path)…
Generates a security status report based on docs/threats.json by spinning up sub-agents for each threat to compute a quality score.
Install Security Status Report
$ npx skills add agent-substrate/substrate --skill security-status-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agent-substrate/substrate security-status-report --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/agent-substrate/substrate.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/security-status-report .claude/skills/security-status-report && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "security-status-report" agent skill from https://github.com/agent-substrate/substrate/tree/main/.agents/skills/security-status-report into .claude/skills/security-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-status-report", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/agent-substrate/substrate/tree/main/.agents/skills/security-status-reportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add agent-substrate/substrate --skill security-status-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agent-substrate/substrate security-status-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agent-substrate/substrate.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/security-status-report .agents/skills/security-status-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "security-status-report" agent skill from https://github.com/agent-substrate/substrate/tree/main/.agents/skills/security-status-report into .agents/skills/security-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-status-report", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agent-substrate/substrate --skill security-status-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agent-substrate/substrate security-status-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agent-substrate/substrate.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/security-status-report .cursor/skills/security-status-report && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "security-status-report" agent skill from https://github.com/agent-substrate/substrate/tree/main/.agents/skills/security-status-report into .cursor/skills/security-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-status-report", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/agent-substrate/substrate.git --path .agents/skills/security-status-report--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add agent-substrate/substrate --skill security-status-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agent-substrate/substrate security-status-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agent-substrate/substrate.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/security-status-report .gemini/skills/security-status-report && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "security-status-report" agent skill from https://github.com/agent-substrate/substrate/tree/main/.agents/skills/security-status-report into .gemini/skills/security-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-status-report", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install agent-substrate/substrate security-status-reportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add agent-substrate/substrate --skill security-status-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agent-substrate/substrate.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/security-status-report .github/skills/security-status-report && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "security-status-report" agent skill from https://github.com/agent-substrate/substrate/tree/main/.agents/skills/security-status-report into .github/skills/security-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-status-report", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agent-substrate/substrate --skill security-status-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agent-substrate/substrate security-status-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agent-substrate/substrate.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/security-status-report .opencode/skills/security-status-report && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "security-status-report" agent skill from https://github.com/agent-substrate/substrate/tree/main/.agents/skills/security-status-report into .opencode/skills/security-status-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-status-report", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
security-status-report- GitHub stars
- 4.5k
- Token cost
- ~524 tokens
- SKILL.md length
- 201 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Generates a security status report based on docs/threats.json by spinning up sub-agents for each threat to compute a quality score.
- Works in 7 steps: Copy… → Complete the TODO in… → Execute the script from the repository… → …
- Tasks that involve Subagents
- Runs Python scripts from its folder; calls python3
What it does
Security Status Report is an agent skill from agent-substrate/substrate. Generates a security status report based on docs/threats.json by spinning up sub-agents for each threat to compute a quality score.
Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/compile_report.py`, `scripts/render_chart.py` and `scripts/template_dispatch.py`).
It sits in Agent Workflows, covering Subagents. It works with Python. The repository describes itself as: Agent Substrate: the core system. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Subagents
Example prompts
- “Use the security-status-report skill to generate a security status report based on docs/threats.json by spinning up sub-agents for each threat to…”
- “/security-status-report”
Requirements
- Python 3
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- 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
- Execute the script from the repository root, specifying .agents/scratch/security-status-report/subagents.json as the output file argument…
- Read .agents/scratch/security-status-report/subagents.json and copy its exact JSON array into your tool for invoking subagents. DO NOT…
- 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…
- Run python3 .agents/skills/security-status-report/scripts/render_chart.py .agents/scratch/security-status-report/final.json…
What it can do on your machine
Read from SKILL.md and the folder at commit 0b91488. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Security Status Report loads about 524 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 201 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from agent-substrate/substrate at commit 0b91488, republished under its Apache-2.0 licence (© agent-substrate). 201 words, ~524 tokens.
Download SKILL.mdSave it as
.claude/skills/security-status-report/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- security-status-report
- description
- Generates a security status report based on docs/threats.json by spinning up sub-agents for each threat to compute a quality score.
Task
Generate a security status report by evaluating threats listed in docs/threats.json.
Workflow
- Copy
.agents/skills/security-status-report/scripts/template_dispatch.pyto.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 fromdocs/threats.jsonto 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.jsonas 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.jsonand 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.jsonto 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.pngto render a bar chart of the scores.
© agent-substrate, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in .agents/skills/security-status-report of agent-substrate/substrate.
- SKILL.md
- scripts/compile_report.py
- scripts/render_chart.py
- scripts/template_dispatch.py
Open the folder on GitHubat commit 0b91488
Compare with similar skills
Security Status Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Security Status Report this skillagent-substrate/substrate | 4.5k | — | ~524 | Automated safety check: Pass | Apache-2.0 | |
| Claude Statusbarleeguooooo/claude-code-usage-bar | 377 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Migrating Claude Agent SDK To Pydantic AIpydantic/pydantic-ai | 20k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Extracting Requirementsprime-radiant-inc/iterative-development | 181 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| agystack Runtime Setupjtaroreh/agystack | 103 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Subagent-Driven DevelopmentHoangNguyen0403/agent-skills-standard | 570 | — | ~852 | Automated safety check: Pass | MIT |
Similar skills
- Official
Migrating Claude Agent SDK To Pydantic AI
pydantic/pydantic-ai
Migrate Python applications from the Claude Agent SDK to Pydantic AI and, only when needed, Pydantic AI Harness.
Extracting Requirements
prime-radiant-inc/iterative-development
Reads human-written spec documents and produces per-epic requirement files with proof obligations plus behavior scenarios with stable IDs, using parallel chunked extraction.
agystack Runtime Setup
jtaroreh/agystack
Configures agystack's model tiers per role and its execution runtime, choosing between local subagents and Cloud Run jobs for large parallel swarms.
Subagent-Driven Development
HoangNguyen0403/agent-skills-standard
Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.
- Official
Pydantic AI Harness
pydantic/skills
Extend Pydantic AI agents with batteries-included capabilities from pydantic-ai-harness -- Code Mode (collapse many tool calls into one sandboxed Python execution), a filesystem and shell…
More from agent-substrate/substrate
Post Draft Review
agent-substrate/substrate
Posts pull request review findings as GitHub draft (pending) inline comments for a human to edit and submit, instead of publishing them straight to the PR author.
Triage Issues
agent-substrate/substrate
Triages open GitHub issues by applying the correct labels. An agent skill from agent-substrate/substrate.
Detect Flaky Tests
agent-substrate/substrate
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM…
Review Crds
agent-substrate/substrate
Reviews CRDs for compliance with Kubernetes API conventions.
Agents Md
agent-substrate/substrate
Generates or updates an AGENTS.md file
Related
Works with
Categories
Questions about Security Status Report
What does Security Status Report do?
Generates a security status report based on docs/threats.json by spinning up sub-agents for each threat to compute a quality score. Security Status Report is an agent skill from agent-substrate/substrate.json by spinning up sub-agents for each threat to compute a quality score.
When should I use Security Status Report?
Security Status Report fits situations like: tasks that involve Subagents.
How do I install Security Status Report in Claude Code?
Run `npx skills add agent-substrate/substrate --skill security-status-report -a claude-code`. Or copy the skill folder (.agents/skills/security-status-report in agent-substrate/substrate) into .claude/skills/security-status-report in your project. Claude Code loads it when a task matches its description.
How do I install Security Status Report in Codex?
Run `npx skills add agent-substrate/substrate --skill security-status-report -a codex`. Or copy the skill folder (.agents/skills/security-status-report in agent-substrate/substrate) into .agents/skills/security-status-report in your project. Codex loads it when a task matches its description.
Can I use Security Status Report in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agent-substrate/substrate --skill security-status-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/security-status-report, .gemini/skills/security-status-report, .github/skills/security-status-report and .opencode/skills/security-status-report in your project.
What does Security Status Report need to run?
Going by SKILL.md and its folder, Security Status Report needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Security Status Report access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Security Status Report safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Security Status Report use?
Security Status Report is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Security Status Report use?
About 524 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Security Status Report?
Skills that share tags, products or a category with Security Status Report: Claude Statusbar (leeguooooo/claude-code-usage-bar, 377 stars), Migrating Claude Agent SDK To Pydantic AI (pydantic/pydantic-ai, 20k stars), Extracting Requirements (prime-radiant-inc/iterative-development, 181 stars) and agystack Runtime Setup (jtaroreh/agystack, 103 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Security Status Report?
agent-substrate (a GitHub organization) maintains it in agent-substrate/substrate, which has 4,459 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.
Source: agent-substrate/substrate on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.