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 skills/evilfreelancer/secs/mapping-attack-techniquesnpx skills add EvilFreelancer/secs --skill mapping-attack-techniquesgit clone --depth 1 https://github.com/EvilFreelancer/secsWhat 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.00096 | $0.02096 |
| Opus 5 | $0.00048 | $0.01048 |
| Sonnet 5 | $0.00019 | $0.00419 |
| Haiku 4.5 | $0.00010 | $0.00210 |
Grade A, and why
mapping-attack-techniques scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL "https://defuddle.md/<url>" # scheme in the path is optional This is a copy
100% identical to mapping-attack-techniques — 0 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mapping ATT&CK Techniques
ATT&CK is a shared vocabulary, not a methodology. Its value is that offense, detection, and response can name the same behaviour — which makes this skill a router, not a technique catalogue. It resolves a technique to the skill that holds the actual procedure, and it runs the loop that connects the two sides.
When to Use
- A request names a technique ID (
T1003.001), a technique name ("Kerberoasting"), or a tactic ("we need lateral movement coverage") - Converting a threat intel report or an adversary emulation plan into work
- Planning or reporting coverage against the matrix
- Running a purple team exercise: emulate, detect, validate, close the gap
- Choosing which skill applies when a request spans offense and defense
When NOT to Use
- A plain-language request ("dump creds off this host") — the domain skills trigger directly on that; routing through here adds a hop for nothing
- Code-level vulnerability work — ATT&CK does not model source defects; use
auditing-code-for-vulnerabilitieswith CWE and ASVS instead - AI/LLM systems — use
securing-ai-systems; the framework there is MITRE ATLAS, not ATT&CK Enterprise - Mobile targets —
testing-mobile-applications; the Mobile matrix has its own IDs that do not correspond to Enterprise ones
The Index
secskills-core/ttp-index.json maps techniques to the skills that cover them. Read
it directly to resolve a lookup:
# Which skill covers this technique?
python3 -c "
import json;d=json.load(open('secskills-core/ttp-index.json'))
print([r for r in d['techniques'] if r['id']=='T1003.001'])"
# Everything under one tactic
python3 -c "
import json;d=json.load(open('secskills-core/ttp-index.json'))
[print(r['id'], r['name'], '→', ', '.join(r['skills']))
for r in d['techniques'] if 'TA0008' in r['tactics']]"
# Search by name when you have words, not an ID
rg -i 'kerberoast|pass the hash' secskills-core/ttp-index.json
Each skill also carries a generated ## ATT&CK Coverage section listing its
techniques. That section and the index are kept in sync by
scripts/sync_attack.py; the index is the source of truth.
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.
- 2d ago First seen · 186 lines · 96 tokens per session scan A 9f4c6079013b
mapping-attack-techniques is a skill published in the GitHub repository EvilFreelancer/secs (10 stars, last pushed 23d ago), licensed Apache-2.0. It adds 96 tokens to every session and 2,096 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to mapping-attack-techniques, differing in 0 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-email-headers-for-phishing-investigation
Parse and analyze email headers to trace the origin of phishing emails, verify sender authenticity, and identify spoofing through SPF, DKIM, and DMARC validation.
analyzing-prefetch-files-for-execution-history
Parse Windows Prefetch files to determine program execution history including run counts, timestamps, and referenced files for forensic investigation.
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware using Ghidra with specialized scripts for function recovery, string extraction, and type reconstruction in stripped Go binaries.
analyzing-ios-app-security-with-objection
Performs runtime mobile security exploration of iOS applications using Objection, a Frida-powered toolkit that enables security testers to interact with app internals without jailbreaking. Use when assessing iOS app security posture, bypassing client-side protections, dumping keychain items, inspecting filesystem…
add-tool
Use when adding a new cybersecurity tool to this installer. Walks through editing the right module file, adding to toolsconfig.json, running validators, and syncing MCP server data if needed. Triggers on phrases like "add tool", "add ", "register a new tool", "include X in the installer".