Borrowing it
Nothing to install: this file belongs to rossoctl/examples. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rossoctl/examples/main/.claude/skills/skills:scan/SKILL.mdgit clone --depth 1 https://github.com/rossoctl/examplesWrote 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/rossoctl/examples/skills-scan)<a href="https://agentmods.dev/skills/rossoctl/examples/skills-scan"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/skills-scan/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/rossoctl/examples/skills-scan"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/skills-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 8 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Rogue Agent · line 210 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Excessive Agency · line 94 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 95 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 96 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 117 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 138 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 218 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00017 | $0.01885 |
| Opus 5.5 | $0.00007 | $0.00754 |
| Sonnet 5.5 | $0.00003 | $0.00377 |
| Haiku 4.5 | $0.00002 | $0.00188 |
Grade A, and why
skills:scan 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan Repository for Skills
Bootstrap skills for a new repo, or audit and update skills in an existing one.
flowchart TD
START(["/skills:scan"]) --> MODE{"Repo has skills?"}
MODE -->|No| NP1["Analyze Repo"]:::skills
MODE -->|Yes| EP1["Validate Existing"]:::skills
NP1 --> NP2["Identify Categories"]:::skills
NP2 --> NP3["Generate Core Skills"]:::skills
NP3 --> NP4["Generate settings.json"]:::skills
NP4 --> DONE([Skills bootstrapped])
EP1 --> EP2["Gap Analysis"]:::skills
EP2 --> EP3["Content Quality"]:::skills
EP3 --> EP4["Connection Analysis"]:::skills
EP4 --> EP5["Usefulness Rating"]:::skills
EP5 --> EP6["Generate Report"]:::skills
EP6 --> EP7["Update README"]:::skills
EP1 -->|Issues| WRITE["skills:write"]:::skills
EP6 -->|Gaps| WRITE
classDef skills fill:#607D8B,stroke:#333,color:white
When to Use
- Setting up Claude Code skills in a new repository
- Auditing an existing repo for skill gaps
- Updating skills after the repo's tech stack or workflows changed
- Onboarding to a new codebase
Mode: New Repo (no .claude/skills/ exists)
Phase 1: Analyze Repository Structure
Scan for technology markers:
ls -la Makefile pyproject.toml package.json Cargo.toml go.mod pom.xml 2>/dev/null
Check CI configuration:
ls .github/workflows/ .gitlab-ci.yml Jenkinsfile .circleci/ 2>/dev/null
Check deployment patterns:
ls -d charts/ helm/ k8s/ kubernetes/ deployments/ docker-compose* Dockerfile 2>/dev/null
Check test structure:
find . -type d -name "tests" -o -name "test" -o -name "__tests__" -o -name "e2e" 2>/dev/null | head -10
Phase 2: Identify Skill Categories
Based on findings, propose categories:
| Marker | Suggested Skills |
|---|---|
.github/workflows/ |
CI-related skills (status, monitoring) |
charts/ or helm/ |
Helm debugging skills |
Dockerfile |
Docker build/debug skills |
tests/e2e/ |
TDD and RCA skills |
deployments/ansible/ |
Ansible deploy skills |
| Kubernetes manifests | K8s health, pod, and log skills |
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 · 244 lines · 17 tokens per session scan A c0d4013adf34
skills:scan is a skill published in the GitHub repository rossoctl/examples (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 1,885 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-08-30.
Other skills, from other repositories
testing-patterns
Redirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-unit, testing-e2e, testing-integration, testing-llm, or testing-perf.
cortex-query
This skill has been consolidated into cortex-engine.
gr-seo-geo-agent
A pointer to another SEO and AI-search visibility skill. It does not contain the full workflow itself.
mk:lazy-agent-loader
Deprecated compatibility shim. Agent routing reads the canonical inventory under .claude/agents/ directly; do not use this skill for agent selection.
gbrain-integration-{{AGENT_NAME_LOWER}}
⚠️ DEPRECATED — gbrain replaced by SQLite FTS5 + Ollama embeddings (2026-07-05). Use recall()/remember() tools instead.
cortex-review
This skill has been consolidated into cortex-engine.