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-pcap-analysisgit 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-pcap-analysis)<a href="https://agentmods.dev/skills/zhang-henry/coevoskills/evo-pcap-analysis"><img src="https://agentmods.dev/badge/skills/zhang-henry/coevoskills/evo-pcap-analysis/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-pcap-analysis"><img src="https://agentmods.dev/badge/skills/zhang-henry/coevoskills/evo-pcap-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.00438 |
| Opus 5 | $0.00024 | $0.00219 |
| Sonnet 5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
evo-pcap-analysis 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 12d 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.
What it actually says
PCAP Network Statistics Analysis
This skill analyzes PCAP files and fills a CSV template with computed network statistics. Metric names are discovered from the template at runtime - no hardcoded metric names.
Quick Start
import sys
sys.path.insert(0, '/app/environment/skills/evo-pcap-analysis/scripts')
from pcap_stats import run_end_to_end
pcap_path = '/root/packets.pcap'
template_path = '/root/network_stats.csv'
output_path = '/root/network_stats.csv'
results, ok = run_end_to_end(pcap_path, template_path, output_path)
if not ok:
print("Validation failed!")
else:
print("Done - all metrics filled")
Architecture
load_packets(path)- Load PCAP with Scapy (handles VLAN, tunnels)count_protocols(packets)- Independent layer checks per protocolcompute_rate_buckets(timestamps, bucket_size)- Relative time bucketingcompute_size_stats(packets)- Full frame length statsshannon_entropy(values)- Shannon entropy in bitscompute_graph(packets)- Directed IP graph topologycompute_iat(timestamps)- Inter-arrival time with population variancecompute_pcr(packets)- Producer/Consumer ratio per IPcompute_flows(packets)- 5-tuple flow analysisdetect_port_scan(packets)- Converging evidence detectiondetect_dos(buckets)- Rate spike detectiondetect_beaconing(iat_stats)- Low CV detectionresolve_metric(name, computed)- Dynamic name-to-value resolutionanalyze_and_resolve(pcap, template)- Full pipeline with template discoveryvalidate_csv(path)- Check all template lines have values
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.
- 12d ago First seen · 46 lines · 49 tokens per session scan A 26e239dfe84e
evo-pcap-analysis is a skill published in the GitHub repository Zhang-Henry/CoEvoSkills (66 stars, last pushed 22d ago), licensed Apache-2.0. It adds 49 tokens to every session and 438 once invoked, about $0.0002 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…