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 EvilFreelancer/secs --skill vetting-agent-extensionsgit clone --depth 1 https://github.com/EvilFreelancer/secsWrote 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/evilfreelancer/secs/vetting-agent-extensions)<a href="https://agentmods.dev/skills/evilfreelancer/secs/vetting-agent-extensions"><img src="https://agentmods.dev/badge/skills/evilfreelancer/secs/vetting-agent-extensions.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.1 | $0.00110 | $0.02920 |
| Opus 5 | $0.00055 | $0.01460 |
| Sonnet 5 | $0.00022 | $0.00584 |
| Haiku 4.5 | $0.00011 | $0.00292 |
Grade C, and why
vetting-agent-extensions scanned grade C with 2 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 7d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
runs it is a `curl | bash` with extra steps; the question is whether the Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
runs it is a `curl | bash` with extra steps; the question is whether the This is a copy
98% identical to vetting-agent-extensions — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vetting Agent Extensions
An agent extension is not a library you call — it is text and configuration that your model reads as instructions and tooling your agent runs on your behalf. A malicious dependency has to wait for you to call it. A malicious skill is already in the context window, and a malicious MCP server may execute the moment the agent starts. The trust decision happens before either runs, and it is the decision this skill is about.
This is an adoption gate, not a code audit. The question is not "does this server have a CVE" — it is "if I install this, what can it make my agent do, and what can it read on its way out."
When to Use
- Deciding whether to install a skill pack, plugin, or marketplace entry into Claude Code, Cursor, Cline, or a similar agent
- Reviewing an MCP server before adding it to an agent's config — especially
one that ships its own
.mcp.json,.env, or startup wiring - Judging a repo that mixes skills, MCP config, and bootstrap scripts, where installing the repo wires all three at once
- Assessing whether third-party agent content that gets loaded into context (skill bodies, tool descriptions, resources, bundled notes) can steer the model or leak the current engagement
When NOT to Use
- Auditing an MCP server's own code for vulnerabilities — injection
surfaces, tool scope, authz, transport — use
auditing-mcp-servers. That skill reviews a server you are building or breaking; this one decides whether to trust one someone else built. - Dependency, package, lockfile, and CI/CD supply-chain risk — use
auditing-supply-chain. An extension's npm/pip dependencies are its problem; route them there. - Prompt-injection and tool-abuse testing of an LLM application you are
assessing — use
securing-ai-systems. - Reviewing a diff to an extension you have already adopted — use
auditing-code-for-vulnerabilities; come back here only if the diff changes what loads into context or what runs on startup.
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.
- 7d ago First seen · 238 lines · 110 tokens per session scan C 929d470e202e
vetting-agent-extensions is a skill published in the GitHub repository EvilFreelancer/secs (10 stars, last pushed 29d ago), licensed Apache-2.0. It adds 110 tokens to every session and 2,920 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 98% identical to vetting-agent-extensions, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
analyzing-slack-space-and-file-system-artifacts
Examine file system slack space, MFT entries, USN journal, and alternate data streams to recover hidden data and reconstruct file activity on NTFS volumes.
analyzing-ransomware-encryption-mechanisms
Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify implementation weaknesses, and support recovery efforts. Covers AES, RSA, ChaCha20, and hybrid encryption schemes. Activates for requests involving ransomware…
analyzing-windows-event-logs-in-splunk
Analyzes Windows Security, System, and Sysmon event logs in Splunk to detect authentication attacks, privilege escalation, persistence mechanisms, and lateral movement using SPL queries mapped to MITRE ATT&CK techniques. Use when SOC analysts need to investigate Windows-based threats, build detection queries, or…
building-incident-response-dashboard
Builds real-time incident response dashboards in Splunk, Elastic, or Grafana to provide SOC analysts and leadership with situational awareness during active incidents, tracking affected systems, containment status, IOC spread, and response timeline. Use when IR teams need unified visibility during incident…
bypassing-authentication-with-forced-browsing
Discovering and accessing unprotected pages, APIs, and administrative interfaces by enumerating URLs and bypassing authentication controls during authorized security assessments.