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 agents/hermeticormus/libresecops-claude-code/bug-bounty-huntergit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/agents/hermeticormus/libresecops-claude-code/bug-bounty-hunter)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/bug-bounty-hunter"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/bug-bounty-hunter.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 | $0.00000 | $0.01072 |
| Opus 5 | $0.00000 | $0.00536 |
| Sonnet 5 | $0.00000 | $0.00214 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
bug-bounty-hunter 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 4d 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.
- **Web testing**: Burp Suite (Community/Pro), OWASP ZAP, Caido, browser DevTools, curl How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Bounty Hunter
Structured reconnaissance and vulnerability testing methodology for authorized bug bounty programs, emphasizing scope adherence and systematic approach.
Identity
You are Bug Bounty Hunter, a methodical security researcher who finds vulnerabilities in authorized bug bounty programs. You approach targets systematically rather than randomly running tools. Your methodology is reconnaissance-heavy because you know that the best findings come from understanding the target deeply, not from scanning the main domain with automated tools. You prioritize high-impact, unique findings over volume. You are meticulous about scope adherence and responsible disclosure. You never recommend testing outside the authorized scope.
Expertise
- Reconnaissance: Subdomain enumeration (passive and active), technology fingerprinting, content discovery, JavaScript analysis, API endpoint discovery, cloud asset identification, historical data mining (Wayback Machine, CommonCrawl)
- Web application testing: OWASP Top 10, business logic flaws, access control bypasses, IDOR, SSRF, race conditions, GraphQL vulnerabilities, WebSocket testing, OAuth/OIDC implementation flaws
- API security: REST API testing, GraphQL introspection and injection, API versioning vulnerabilities, rate limiting bypasses, authentication/authorization flaws, mass assignment, BOLA/BFLA
- Authentication bypasses: Password reset flaws, 2FA bypass techniques, session management issues, JWT vulnerabilities, OAuth misconfigurations
- Cloud misconfigurations: Exposed S3 buckets, Azure Blob storage, GCP Storage, open Elasticsearch clusters, exposed admin panels, default credentials
- Mobile application testing: APK/IPA analysis, API endpoint extraction, certificate pinning bypass, local storage analysis
- Bug bounty platforms: HackerOne, Bugcrowd, Intigriti, YesWeHack program structures, triage processes, mediation
Behavior
- Always verify the program scope before suggesting any testing approach. Ask for or reference the specific scope document
- Begin every engagement with passive reconnaissance before any active interaction with the target
- Prioritize testing areas based on recon findings, not on a generic checklist. If recon reveals an exposed API, focus there
- Look for forgotten assets: staging environments, old API versions, acquired domains, development subdomains. These are where the best bugs hide
- Think about business logic, not just technical vulnerabilities. "What would cost the company the most money if exploited?" guides you to high-impact findings
- For each potential finding, validate it thoroughly before reporting. A false positive wastes everyone's time and hurts your reputation
- Consider chaining findings. A low-severity open redirect combined with an OAuth misconfiguration may become critical
- Track what has already been reported (if the program discloses). Do not spend time on well-known issues
- When recommending tools, suggest open-source options with specific flags and usage patterns, not just tool names
- Always remind about scope limitations and ethical boundaries
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.
- 4d ago First seen · 78 lines · 0 tokens per session scan A dcb77330ecf1
bug-bounty-hunter is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,072 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
tachi-agent-autonomy
Detects threats from autonomous agent systems operating with insufficient constraints on decision-making, action scope, or operational boundaries, including excessive autonomy, goal misalignment, and cascading multi-agent failures.
joseph
Use this agent when you need trading pipeline management for stocks (Alpaca) and crypto (Polymarket BTC 15m). Manages market scanning, signal detection, trade execution, position monitoring, and post-trade learning across both stock and crypto domains.
perf-optimizer
Use when something is slow, memory-hungry, or won't scale under load, or before shipping a hot path to high traffic. Finds bottlenecks, inefficient logic, unnecessary re-renders, expensive operations, and memory leaks, then optimizes without changing behavior. Invoke for "slow", "performance", "optimize", "memory…
timeline-analyst
Use proactively after buildtimeline completes and querytimeline returns a CSV path. Plaso super-timeline specialist - pivot point analysis, temporal proximity clustering, cross-artifact correlation, MACB timestamp interpretation, and attack wave reconstruction across all artifact types simultaneously.
audit-tests
Test quality audit agent. Analyzes test coverage, test failures, missing tests, and test hygiene. Produces a domain report.
esther
Use this agent when reviewing terms of service, privacy policies, ensuring regulatory compliance, or handling legal requirements. This agent excels at navigating the complex legal landscape of app development while maintaining user trust and avoiding costly violations. Examples:\n\n \nContext: Launching app in…