eval-security

A command for checking a skill's instructions for security problems. It examines the instructions and, when available, uses approved local checking tools and configured custom checks.

In plain words
What is it for?
Use it to scan a skill file and report security findings, with an optional verbose mode for showing lower-severity issues.
Why use it?
It helps find unsafe or suspicious instructions before the skill is used. The scan combines built-in checks with additional approved checks and removes duplicate findings.

Command

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 commands/evol-ai/skillcompass/eval-security
Clone the repo
git clone --depth 1 https://github.com/Evol-ai/SkillCompass
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 625 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00625
Opus 5 $0.00000 $0.00313
Sonnet 5 $0.00000 $0.00125
Haiku 4.5 $0.00000 $0.00063

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

Security

Grade A, and why

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

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.

commands/eval-security.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/eval-security — Standalone Security Scan

Locale: All templates in this spec are written in English. Detect the user's language from the session and translate user-facing text at display time per SKILL.md's Global UX Rules. Dimension labels: see the canonical table in SKILL.md.

Arguments

  • <path> (required): Path to the SKILL.md file to scan.
  • --verbose (optional): Show detailed findings including low severity.

Steps

Step 1: Load Target

Parse arguments. Use the Read tool to load the target SKILL.md file.

Step 2: L0 Built-in Scan

Use the Read tool to load {baseDir}/prompts/d3-security.md. Execute all 7 L0 check categories against the target skill content. Record findings.

Step 3: L1/L2 External Tools

Use the Read tool to load {baseDir}/shared/tool-instructions.md. Follow the L1 whitelist detection procedure: for each tool, use the Bash tool to check if installed, and invoke if found. Then check .skill-compass/config.json for L2 custom tools and invoke those.

Step 4: Aggregate

Merge all findings from L0 + L1 + L2. Deduplicate by (location, check_type), keeping highest severity. Add source field to each finding.

Step 5: Output

Output the D3 section of the evaluation result (conforming to the security portion of schemas/eval-result.json):

{
  "dimension": "D3",
  "dimension_name": "security",
  "score": 8,
  "max": 10,
  "pass": true,
  "findings": [],
  "tools_used": ["builtin"],
  "details": "..."
}

If --verbose is not set: omit findings with severity "low" from display (still count them in score).

After printing the result:

  • Findings exist AND neither --internal nor --ci is set: print a status line then present choices:

    ⚠ {N} security issue(s) found.
    [Fix security issues / View details / Done]
    
    • Fix security issues — invoke the fix workflow to address reported findings.
    • View details — re-display all findings including those hidden by verbosity rules.
    • Done — exit with no further action.

Read the full file on GitHub · 71 lines

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. 2d ago First seen · 71 lines · 0 tokens per session scan A 165b4023aeb6

Subscribe to this mod's changes

eval-security is a command published in the GitHub repository Evol-ai/SkillCompass (215 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 625 tokens. 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.