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.
npx agentmods add commands/evol-ai/skillcompass/eval-mergegit clone --depth 1 https://github.com/Evol-ai/SkillCompassWrote 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/commands/evol-ai/skillcompass/eval-merge)<a href="https://agentmods.dev/commands/evol-ai/skillcompass/eval-merge"><img src="https://agentmods.dev/badge/commands/evol-ai/skillcompass/eval-merge.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.00924 |
| Opus 5 | $0.00000 | $0.00462 |
| Sonnet 5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
eval-merge 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 4d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/eval-merge — Three-Way Version Merge
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 (local evo version).--upstream <path-or-url>(optional): Path to upstream version. If omitted, detect from manifest.--internal(optional): Skip interactive prompts; use defaults for automated pipelines.--ci(optional): Alias for--internal.
Pre-conditions
Use the Read tool to load .skill-compass/{skill-name}/manifest.json. Verify:
upstream_originexists in manifest (skill has a known upstream source)- At least 1 evo version exists (something to preserve)
- Upstream version differs from last known upstream (there IS an update)
If any pre-condition fails: display the failure reason in the session locale and stop. Do not show raw error codes or internal field names — describe the problem and, where possible, suggest what the user can do next.
Steps
Step 1: Identify Three Versions
- Base: the last known upstream version from manifest (
upstream_origin.last_known_version). Load from snapshots. - Local: the current evo version (the file at
<path>). - Upstream: the new upstream version (from
--upstreamflag or auto-detected).
Use the Read tool to load all three versions.
Step 2: Execute Merge
Use the Read tool to load {baseDir}/prompts/merge.md. Pass:
{BASE_VERSION}: base content{LOCAL_VERSION}: local content{UPSTREAM_VERSION}: upstream content
Follow the merge prompt's region-by-region strategy. Present conflicts to the user for resolution.
Step 3: Write Merged Version
After all conflicts resolved, display the complete merged SKILL.md. Ask user for confirmation before writing.
If confirmed: use the Write tool to save the merged version.
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.
- 4d ago First seen · 92 lines · 0 tokens per session scan A 803e842f636f
eval-merge 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 924 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.
Other commands, from other repositories
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
reskin
Extract a measured design signature (type ramp, accent + its budget, grid unit, radius, layout) from a reference image or site, write it to signature.json, and drive the build to match it — "steal this vibe" as a spec, not pixels.
good
Write good creative & smart copy [GOOD].
enum-udp
UDP scan + service follow-up — top ports first, full sweep only when justified.
kerberos
Kerberos attacks — AS-REP roasting and Kerberoasting.
open-day
Morning kickoff. Load today's context, review yesterday, surface open tasks, identify priorities, and create today's daily note in plan/.