credential-attack SKILL.md skillA

credential-attack from dragonked2/alphacode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add dragonked2/alphacode/credential-attack@git:20261002.de4d363

Pins git:20261002.de4d363 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
dragonked2/alphacode
Path
src/alphacode_base/bundled_skills/bugbounty/credential-attack/SKILL.md
Versions recorded
3
Latest version
git:20261002.de4d363, committed Oct 2, 2026
First version recorded
Sep 23, 2026
Size
10,236 bytes
Repository stars
626
License
MIT

Password spray methodology for bug bounty — when to do it vs web-vuln hunting, the wordlist-gen + breach-check + osint-employees + spray pipeline, mode selection (http-form / oauth / o365 / okta), rate-limit + lockout tactics, legal guardrails, success detection, and the spray → authenticated /hunt chain pattern.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# CREDENTIAL ATTACK PIPELINE

Real-world initial-access vector. Verizon DBIR consistently ranks Stolen Credentials in the top 3 incident types. Most BB hunters skip this because they only try `rockyou.txt` and get rate-limited.

**Core principle:** humans pick lazy passwords. `{CompanyName}{Year}!`, `{ProductName}{Season}`, `{City}123`. Harvesting company-specific vocabulary before spraying is what makes the hit-rate go from 0.01% to 1%+.

---

## WHEN TO RUN CREDENTIAL ATTACK

Credential attack is a **parallel branch** to `/hunt`, not a replacement:

```
/recon ──┬──▶ /hunt (web vuln scan) ──┐
         │                             ├──▶ /validate ──▶ /report
         └──▶ /wordlist-gen → ... → /spray ──┘
```

**Run it when:**
- Target has a discoverable login endpoint (web form / O365 / Okta / OAuth)
- Program scope **explicitly permits** authentication testing or credential testing
- You can stomach a 30-min-to-multi-hour run (with conservative defaults)

**Skip it when:**
- Program policy lists "credential stuffing", "brute force", or "password attacks" as out-of-scope
- Target only has SSO via a provider you don't control
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xithq5uaggo35pdr/0ff9abf728b79c91b7bcbc05c463279325337158288424ae41dab51469e3c964.json

Then /plugin install credential-attack@markdownregistry-xithq5uaggo35pdr in Claude Code. It installs git:20261002.de4d363, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add dragonked2/alphacode/credential-attack@sha256:0ff9abf728b79c91

The line at the top of this page pins the label git:20261002.de4d363, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_xithq5uaggo35pdr.svg)](https://markdownregistry.com/a/art_xithq5uaggo35pdr)

5 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in dragonked2/alphacode/credential-attack since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of credential-attack from somewhere else? Ask it: where did my credential-attack come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 3 versions of this file, between Sep 23, 2026 and Oct 2, 2026, about one every 5 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261002.de4d363 latest2026-10-02 de4d363 10,236 BA view · diff
git:20260929.29bbcb82026-09-29 29bbcb8 7,344 BA view · diff
git:20260923.82a41432026-09-23 82a4143 6,947 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (10236 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

dragonked2/alphacode · 626 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_xithq5uaggo35pdr
GET https://markdownregistry.com/api/v1/resolve?ref=dragonked2/alphacode/credential-attack
GET https://markdownregistry.com/api/v1/blob/0ff9abf728b79c91b7bcbc05c463279325337158288424ae41dab51469e3c964

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from dragonked2/alphacode

AGENTS.md AGENTS.md file
dragonked2/alphacode · AGENTS.md
git:20261111.5b671c4 · audit A · 626 stars
api-builder SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/api-builder/SKILL.md · Expert REST API design and implementation — endpoint design, authentication, error handling, rate limiting, versioning…
git:20260923.ffaa29c · audit A · 626 stars
api-design SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/api-design/SKILL.md · RESTful and GraphQL API design: OpenAPI specs, pagination, rate limiting, error schemas, versioning, and backwards…
git:20260923.ffaa29c · audit A · 626 stars
api-security SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/api-security/SKILL.md · API security testing: authentication bypass, authorization flaws, rate limiting, input validation, GraphQL…
git:20260923.ffaa29c · audit A · 626 stars
architecture-review SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/architecture-review/SKILL.md · Review system architecture: module boundaries, dependency direction, coupling analysis, and scalability assessment.
git:20260923.ffaa29c · audit A · 626 stars
backend-dev SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/backend-dev/SKILL.md · Comprehensive backend development methodology covering API design, authentication, database design, caching, testing…
git:20260923.ffaa29c · audit A · 626 stars
backend-dev/auth SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/backend-dev/auth/SKILL.md · Authentication and authorization — JWT access/refresh token rotation, OAuth2 PKCE/client credentials, session…
git:20260923.82a4143 · audit A · 626 stars
backend-dev/caching SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/backend-dev/caching/SKILL.md · Caching strategies — HTTP caching, CDN, application-level caching (Redis, Memcached), cache invalidation patterns…
git:20260923.82a4143 · audit A · 626 stars
backend-dev/database SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/backend-dev/database/SKILL.md · Database patterns — schema design, indexing strategies, query optimization, connection pooling, migration management…
git:20260923.82a4143 · audit A · 626 stars
backend-dev/nodejs SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/backend-dev/nodejs/SKILL.md · Node.js/Express/Fastify backend development — project structure, middleware patterns, route design, validation…
git:20260923.82a4143 · audit A · 626 stars
backend-dev/python SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/backend-dev/python/SKILL.md · Python/FastAPI/Django backend development — async patterns, Pydantic models, dependency injection, middleware…
git:20260923.82a4143 · audit A · 626 stars
backend-dev/rust SKILL.md skill
dragonked2/alphacode · src/alphacode_base/bundled_skills/backend-dev/rust/SKILL.md · Rust/Axum/Actix-web backend development — handler patterns, extractors, middleware, error handling, state management…
git:20260923.82a4143 · audit A · 626 stars

Every file in dragonked2/alphacode

Browse by kind, by grade A, or by owner.