defect-hunting SKILL.md skillA
defect-hunting from vmobifystudio/app-dev-team is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vmobifystudio/app-dev-team/defect-hunting@git:20260810.958b327Pins git:20260810.958b327 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vmobifystudio/app-dev-team
- Path
skills/defect-hunting/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260810.958b327, committed Aug 10, 2026
- First version recorded
- Jul 29, 2026
- Size
- 20,418 bytes
- Repository stars
- 5
- License
- MIT
Use when reviewing code, auditing an app, writing a guard rule or test, or certifying any threshold/constant/formula. Finds the defects a diff review structurally cannot see — the second write path, the mis-calibrated constant, the rule that cannot fail. Triggers from code-reviewer, /app-audit, qa-engineer, verification-engineer, and any task that adds a lint rule, architecture test, or CI grep.
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
# Defect hunting Mined from a real remediation programme where twelve screen-by-screen review rounds found nothing new, and one round organised differently found dozens of live defects. Every one of these rules is paid for. **The sentence that generates all four:** > Verify the thing that has to be true, not the thing you changed. Filtering the list is not filtering the parser. Capping the severity is not capping its renderer. Matching the token is not matching the value. Mutating the file is not confirming the mutation landed. --- ## 1. Audit the data's entry points, not the screens A review organised by screen structurally cannot find these, because in every case **the audited surface was correct and the bug was in the second path to the same data** — usually another file, often another module: | What was reviewed | Where the defect actually was | |---|---| | Add-form validation | the **edit** path, which validated nothing | | the dashboard alert banner | the **detail screen** the banner opens — they disagreed | | the growth-target reader | the **writer**, which destroyed data | | the photo picker's success branch | its **cancel** branch, which wiped the existing photo | …
Read the whole file at its exact version.
How to install
mdr add vmobifystudio/app-dev-team/defect-hunting@sha256:4cf94d0107e1a8feThe line at the top of this page pins the label git:20260810.958b327, 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_zgk46i2qgefron3o)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 29, 2026 and Aug 10, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260810.958b327 latest | 2026-08-10 | 958b327 | 20,418 B | A | view · diff |
| git:20260810.62539d3 | 2026-08-10 | 62539d3 | 20,231 B | A | view · diff |
| git:20260804.a760e21 | 2026-08-04 | a760e21 | 16,256 B | A | view · diff |
| git:20260729.9d76795 | 2026-07-29 | 9d76795 | 11,412 B | A | view · diff |
| git:20260729.198ad79 | 2026-07-29 | 198ad79 | 9,874 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 (20418 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
vmobifystudio/app-dev-team · 5 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zgk46i2qgefron3o GET https://markdownregistry.com/api/v1/resolve?ref=vmobifystudio/app-dev-team/defect-hunting GET https://markdownregistry.com/api/v1/blob/4cf94d0107e1a8fef7f9d7ff60544e9994654a89028a07a9656384c354dd830d
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.