Bruteforce Database is a collection of wordlists, meaning lists of possible passwords, usernames, paths, and other values used in security testing. It is for authorized penetration testing, password analysis, account enumeration, and web or infrastructure discovery. Its catalogue instruction relates to using these wordlists in security-testing workflows.
Borrowing it
Nothing to install: this file belongs to duyet/bruteforce-database. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/duyet/bruteforce-database/master/CLAUDE.mdgit clone --depth 1 https://github.com/duyet/bruteforce-databaseWrote 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/instructions/duyet/bruteforce-database/claude-md)<a href="https://agentmods.dev/instructions/duyet/bruteforce-database/claude-md"><img src="https://agentmods.dev/badge/instructions/duyet/bruteforce-database/claude-md/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/instructions/duyet/bruteforce-database/claude-md"><img src="https://agentmods.dev/badge/instructions/duyet/bruteforce-database/claude-md.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.01151 | $0.01151 |
| Opus 5.5 | $0.00460 | $0.00460 |
| Sonnet 5.5 | $0.00230 | $0.00230 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
bruteforce-database CLAUDE.md 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 1mo 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE - Project Philosophy & Principles
Community Led Archive of Universal Dictionaries for Ethical Security
The Vision
This is not just a collection of text files. This is a living archive maintained by the security community, for the security community.
Every wordlist tells a story. Every password represents a pattern in human behavior. Every username is a glimpse into digital identity. This repository preserves that knowledge and makes it accessible.
Core Principles
1. Quality Over Quantity
We don't collect every wordlist that exists. We curate the essential sets that security professionals actually need:
- Password dictionaries for brute-force testing
- Username collections for account enumeration
- Subdomain lists for reconnaissance
- Forced-browsing paths for web application testing
Standard: Every wordlist must have clear provenance, documented purpose, and validated quality.
2. Ethical Use
This repository exists to improve security, not undermine it:
- Wordlists help security teams test their defenses
- Penetration testers use these for authorized assessments
- Researchers analyze password patterns to educate users
- Developers test authentication systems against common attacks
Responsibility: We trust our community to use these resources ethically and legally.
3. Transparency
Every entry in this repository should be traceable:
- Where did this wordlist come from?
- When was it collected?
- How many unique entries does it contain?
- What is its intended use case?
Commitment: We maintain a comprehensive manifest with full metadata.
4. Community First
This repository belongs to everyone who contributes:
- Contributors add new wordlists with proper attribution
- Maintainers ensure quality and organization
- Users provide feedback on effectiveness
- The community decides what belongs
Promise: Every contribution is valued, credited, and preserved.
5. Evolution, Not Stagnation
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.
- 1mo ago First seen · 174 lines · 1,151 tokens per session scan A 233b3fd049d3
bruteforce-database CLAUDE.md is an instructions file published in the GitHub repository duyet/bruteforce-database (1,760 stars, last pushed 16d ago), licensed MIT. It adds 1,151 tokens to every session, about $0.0046 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.