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 sanjaysaini1952/BugBounty-Arsenal --skill info-disclosuregit clone --depth 1 https://github.com/sanjaysaini1952/BugBounty-ArsenalWrote 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/sanjaysaini1952/bugbounty-arsenal/info-disclosure)<a href="https://agentmods.dev/skills/sanjaysaini1952/bugbounty-arsenal/info-disclosure"><img src="https://agentmods.dev/badge/skills/sanjaysaini1952/bugbounty-arsenal/info-disclosure/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/sanjaysaini1952/bugbounty-arsenal/info-disclosure"><img src="https://agentmods.dev/badge/skills/sanjaysaini1952/bugbounty-arsenal/info-disclosure.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.00000 | $0.00428 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
info-disclosure 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
Information Disclosure Hunting Skill — 10 Test Cases
Load when: information disclosure, sensitive data, data leakage, exposure.
265. Sensitive data in API responses (easy)
Check all API responses for: full email, phone, address, SSN, credit card, internal IPs, source code, debug info.
266. Sensitive data in error messages (easy)
Trigger errors with invalid input. Check for: stack traces, database errors, internal paths, version info.
267. Sensitive data in headers (easy)
Check response headers for: Server, X-Powered-By, X-AspNet-Version, X-Generator, X-Runtime.
268. Source code disclosure (medium)
Check for: .git, .env, .DS_Store, web.config, application.properties, backup files.
269. Directory listing (easy)
Navigate to directories without index files. Check if directory listing is enabled.
270. Sensitive files exposure (easy)
Check for: /robots.txt, /sitemap.xml, /.env, /config.json, /package.json, /composer.json.
271. Debug endpoints (easy)
Check for: /debug, /console, /admin, /phpinfo.php, /_profiler, /.well-known/.
272. Version information disclosure (easy)
Check for version info in headers, error messages, HTML comments, JavaScript files.
273. Internal IP disclosure (medium)
Check for internal IPs in: response bodies, error messages, JavaScript files, HTML comments.
274. API key exposure in frontend (medium)
Inspect JavaScript source for: API keys, tokens, secrets, passwords in localStorage, cookies, hardcoded values.
Sensitive Files to Check
/robots.txt
/sitemap.xml
/.env
/config.json
/package.json
/composer.json
/.git/config
/web.config
/phpinfo.php
/.DS_Store
/debug
/console
/admin
/.well-known/
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 · 54 lines · 0 tokens per session scan A 2ab60476c75a
info-disclosure is a skill published in the GitHub repository sanjaysaini1952/BugBounty-Arsenal (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 428 tokens. 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-31.
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…