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 skills add Zhang-Henry/CoEvoSkills --skill evo-erlang-ssh-fixgit clone --depth 1 https://github.com/Zhang-Henry/CoEvoSkillsWrote 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/zhang-henry/coevoskills/evo-erlang-ssh-fix)<a href="https://agentmods.dev/skills/zhang-henry/coevoskills/evo-erlang-ssh-fix"><img src="https://agentmods.dev/badge/skills/zhang-henry/coevoskills/evo-erlang-ssh-fix/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/zhang-henry/coevoskills/evo-erlang-ssh-fix"><img src="https://agentmods.dev/badge/skills/zhang-henry/coevoskills/evo-erlang-ssh-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 12 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.00051 | $0.00560 |
| Opus 5 | $0.00026 | $0.00280 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
evo-erlang-ssh-fix 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 11d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Erlang/OTP SSH Pre-Auth Connection Message Vulnerability Fix
Problem
The Erlang/OTP SSH server's ssh_connection_handler.erl processes SSH connection
protocol messages (channel open, channel request, exec, etc.) via {conn_msg, Msg}
internal events WITHOUT checking whether the connection has reached the authenticated
{connected, _} state. An attacker can send crafted SSH connection protocol messages
before completing authentication, causing arbitrary command execution.
Root Cause
In ssh_connection_handler.erl, the handler:
handle_event(internal, {conn_msg,Msg}, StateName, #data{...} = D0) ->
does not guard on ?CONNECTED(StateName). All other capability-bearing handlers
(cast, call) properly use when ?CONNECTED(StateName) guards.
Fix
Insert a guard clause BEFORE the existing conn_msg handler that disconnects
when connection messages arrive in a non-authenticated state:
handle_event(internal, {conn_msg, _Msg}, StateName, _D) when not ?CONNECTED(StateName) ->
?DISCONNECT(?SSH_DISCONNECT_PROTOCOL_ERROR,
"Connection message received before authentication was complete");
This preserves normal authenticated behavior while blocking pre-auth attacks.
Usage
import sys
sys.path.insert(0, '/app/environment/skills/evo-erlang-ssh-fix/scripts')
from utils import run_fix, validate_fix, find_ssh_connection_handler
# End-to-end: find, check, fix, and validate
result = run_fix('/app/workspace/otp_src_27.3.2')
assert result['success'], f"Fix failed: {result['message']}"
# Or validate an already-fixed file
fpath = find_ssh_connection_handler('/app/workspace/otp_src_27.3.2')
validation = validate_fix(fpath)
assert validation['valid'], f"Validation failed: {validation['checks']}"
Key Functions
find_ssh_connection_handler(otp_src_dir)- Locate the file in OTP source treecheck_vulnerability(filepath)- Check if file is vulnerableapply_fix(filepath)- Apply the guard clause fixvalidate_fix(filepath)- Validate fix correctness (clause exists, ordering, etc.)run_fix(otp_src_dir)- End-to-end entry point
What ships with it
1 file 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.
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.
- 11d ago First seen · 62 lines · 51 tokens per session scan A dbdec6e10b49
evo-erlang-ssh-fix is a skill published in the GitHub repository Zhang-Henry/CoEvoSkills (66 stars, last pushed 21d ago), licensed Apache-2.0. It adds 51 tokens to every session and 560 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…