bug-bash SKILL.md skillA
bug-bash from flagrare/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add flagrare/agent-skills/bug-bash@git:20261030.337a593Pins git:20261030.337a593 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- flagrare/agent-skills
- Path
plugins/flagrare/skills/bug-bash/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261030.337a593, committed Oct 30, 2026
- First version recorded
- Jun 3, 2026
- Size
- 20,777 bytes
- Repository stars
- 12
- License
- none declared
Programmatic bug bashing, ingest a prescribed test plan (Notion, markdown, pasted spec), drive a real running system (browser via Chrome DevTools / Playwright MCP, backend via API tools when relevant), run every prescribed case with evidence, then do exploratory passes (viewports, edge inputs, multi-actor flows, codebase-driven concerns, additional context like meeting transcripts, emails and links checked in the real inbox with a control case, other languages, failures and races) without ever…
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
# Bug Bash A disciplined pass through a prescribed test plan against a real running system. The pass ends when every in-scope scenario has been run, every bug has been *reproduced* (not assumed), evidence is captured, and the results have landed where the user wants them. This skill exists because of a specific failure mode: when someone hands you a test plan and a transcript of past discussion, the temptation is to just write up "the team already found these bugs" without actually testing. That produces noise, not signal. The whole point of a bash is that *you ran it and saw it*. --- ## Why this exists Most "QA passes" rot in two directions. Either they're a single happy-path click-through that never finds the interesting bugs, or they're an essay summarizing what other people said in meetings. The first misses real defects; the second pollutes the bug tracker with unverified claims that someone else later has to chase down. A good bash does the prescribed work *and* explores around it *and* keeps a strict line between "I reproduced this" and "someone mentioned this." That line is what makes the output trustworthy. …
Read the whole file at its exact version.
How to install
mdr add flagrare/agent-skills/bug-bash@sha256:9e0d6e3ff63af6b8The line at the top of this page pins the label git:20261030.337a593, 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.
[](https://markdownregistry.com/a/art_edepc4grkqoiwkgr)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 3, 2026 and Oct 30, 2026, about one every 50 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261030.337a593 latest | 2026-10-30 | 337a593 | 20,777 B | A | view · diff |
| git:20260611.9c42181 | 2026-06-11 | 9c42181 | 15,723 B | A | view · diff |
| git:20260611.820c083 | 2026-06-11 | 820c083 | 15,900 B | A | view · diff |
| git:20260603.d084654 | 2026-06-03 | d084654 | 14,647 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (20777 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
flagrare/agent-skills · 12 stars · license none declared · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_edepc4grkqoiwkgr GET https://markdownregistry.com/api/v1/resolve?ref=flagrare/agent-skills/bug-bash GET https://markdownregistry.com/api/v1/blob/9e0d6e3ff63af6b8376dda289724f8487b630e30a67c5ac48a52bf78c790dac5
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 flagrare/agent-skills
Every file in flagrare/agent-skills