Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/26zl/cybersec-toolkitnpx agentmods add skills/26zl/cybersec-toolkit/add-toolWrote 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/26zl/cybersec-toolkit/add-tool)<a href="https://agentmods.dev/skills/26zl/cybersec-toolkit/add-tool"><img src="https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/add-tool.svg" alt="Measured on agentmods" 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.00068 | $0.01248 |
| Opus 5 | $0.00034 | $0.00624 |
| Sonnet 5 | $0.00014 | $0.00250 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
add-tool 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 8d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a new tool to the installer
Use this when the user wants to add a new tool. Follow these steps in order. Do not skip validation.
1. Decide which module the tool belongs to
Match the tool to one of the 18 modules:
| Module | Prefix | Tools |
|---|---|---|
misc.sh |
MISC_ |
General CLI helpers, utilities |
networking.sh |
NET_ |
Scanners, sniffers, proxies |
recon.sh |
RECON_ |
OSINT, subdomain enum, fingerprinting |
web.sh |
WEB_ |
Web app testing, fuzzing, scanners |
crypto.sh |
CRYPTO_ |
Crypto attack tools, analysis |
pwn.sh |
PWN_ |
Binary exploitation, debuggers, fuzzers |
reversing.sh |
RE_ |
Disassemblers, decompilers |
forensics.sh |
FORENSICS_ |
Disk/memory/file forensics |
enterprise.sh |
ENTERPRISE_ |
AD, Kerberos, post-exploit |
wireless.sh |
WIRELESS_ |
Wi-Fi, Bluetooth |
cracking.sh |
CRACKING_ |
Password cracking, hash tools |
stego.sh |
STEGO_ |
Steganography |
cloud.sh |
CLOUD_ |
AWS/GCP/Azure tooling |
containers.sh |
CONTAINER_ |
Docker, k8s |
blueteam.sh |
BLUETEAM_ |
Detection, IR, hardening |
mobile.sh |
MOBILE_ |
APK, iOS analysis |
blockchain.sh |
BLOCKCHAIN_ |
Smart contracts, EVM |
llm.sh |
LLM_ |
AI/LLM testing |
2. Pick the install method
Preferred order: apt > pipx > go > cargo > binary release > gem > Docker > git clone > build from source
Add to the matching array in modules/<module>.sh:
| Method | Array | Format |
|---|---|---|
| apt | <PREFIX>_PACKAGES |
"package-name" |
| pipx | <PREFIX>_PIPX |
"pypi-name" |
| Go | <PREFIX>_GO + <PREFIX>_GO_BINS |
"github.com/owner/repo/cmd@latest" + "binary-name" |
| Cargo | <PREFIX>_CARGO |
"crate-name" |
| Gem | <PREFIX>_GEMS |
"gem-name" |
| Git | <PREFIX>_GIT + <PREFIX>_GIT_NAMES |
"name=https://github.com/owner/repo" + "name" |
| Binary release | BINARY_RELEASES_<MODULE> in lib/installers.sh |
"owner/repo|binary|pattern|dest_dir" |
| Docker | ALL_DOCKER_IMAGES in lib/installers.sh |
"image|label" + add docker_pull call in module install function |
| Build from source | build_from_source call in install_module_*() + <PREFIX>_BUILD_NAMES |
inline |
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.
- 8d ago First seen · 108 lines · 68 tokens per session scan A 00232fe26b88
add-tool is a skill published in the GitHub repository 26zl/cybersec-toolkit (49 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,248 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
mobile-pentest
Mobile app pentest for bug bounty (Android APK + iOS IPA) — runtime-first workflow: install app, proxy through Burp/mitmproxy, drive the UI, capture packets, then test the API exactly like a web target; escalate to decompile (apktool/jadx) and Frida/objection only when traffic is SSL-pinned, encrypted, or absent.…
exploiting-jwt-algorithm-confusion-attack
Exploits JWT algorithm confusion vulnerabilities where the server's token verification library accepts the algorithm specified in the JWT header rather than enforcing a fixed algorithm. The tester manipulates the alg header to switch from RS256 to HS256 (using the RSA public key as the HMAC secret), sets alg to none…
exploiting-excessive-data-exposure-in-api
Tests APIs for excessive data exposure where endpoints return more data than the client application needs, relying on the frontend to filter sensitive fields. The tester intercepts API responses and analyzes them for leaked PII, internal identifiers, debug information, or sensitive business data that the UI does not…
performing-api-fuzzing-with-restler
Uses Microsoft RESTler to perform stateful REST API fuzzing by automatically generating and executing test sequences that exercise API endpoints, discover producer-consumer dependencies between requests, and find security and reliability bugs. The tester compiles an OpenAPI specification into a RESTler fuzzing…
performing-api-inventory-and-discovery
Performs API inventory and discovery to identify all API endpoints in an organization's environment including documented, undocumented, shadow, zombie, and deprecated APIs. The tester uses passive traffic analysis, active scanning, DNS enumeration, JavaScript analysis, and cloud resource inventory to build a…
auditing-gcp-iam-permissions
Auditing Google Cloud Platform IAM permissions to identify overly permissive bindings, primitive role usage, service account key proliferation, and cross-project access risks using gcloud CLI, Policy Analyzer, and IAM Recommender.