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 Njones17/AI-agent-master-cyber-skills-list --skill testing-for-sensitive-data-exposuregit clone --depth 1 https://github.com/Njones17/AI-agent-master-cyber-skills-listWrote 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/njones17/ai-agent-master-cyber-skills-list/testing-for-sensitive-data-exposure)<a href="https://agentmods.dev/skills/njones17/ai-agent-master-cyber-skills-list/testing-for-sensitive-data-exposure"><img src="https://agentmods.dev/badge/skills/njones17/ai-agent-master-cyber-skills-list/testing-for-sensitive-data-exposure/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/njones17/ai-agent-master-cyber-skills-list/testing-for-sensitive-data-exposure"><img src="https://agentmods.dev/badge/skills/njones17/ai-agent-master-cyber-skills-list/testing-for-sensitive-data-exposure.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.03511 |
| Opus 5 | $0.00017 | $0.01755 |
| Sonnet 5 | $0.00007 | $0.00702 |
| Haiku 4.5 | $0.00003 | $0.00351 |
Grade B, and why
testing-for-sensitive-data-exposure scanned grade B 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 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.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
.aws/credentials .docker/config.json; do Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **curl/httpie**: For manual endpoint testing The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 351 lines · 35 tokens per session scan B 85079f7bdec2
testing-for-sensitive-data-exposure is a skill published in the GitHub repository Njones17/AI-agent-master-cyber-skills-list (21 stars, last pushed 6mo ago), with no licence file. It adds 35 tokens to every session and 3,511 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
testing-for-sensitive-data-exposure
Identifying sensitive data exposure vulnerabilities including API key leakage, PII in responses, insecure storage, and unprotected data transmission during security assessments.
exploiting-insecure-deserialization
Identifying and exploiting insecure deserialization vulnerabilities in Java, PHP, Python, and .NET applications to achieve remote code execution during authorized penetration tests.
performing-jwt-none-algorithm-attack
Execute and test the JWT none algorithm attack to bypass signature verification by manipulating the alg header field in JSON Web Tokens.
Web Application Security Testing
OWASP Top 10 testing, injection vulnerability detection, API security assessment, authentication testing, and web vulnerability reporting for authorized assessments.
cwe
Exhaustively test a target against every applicable CWE.
att&ck
Exhaustively test each MITRE ATT&CK technique.