code-forensics-stinger SKILL.md skillA
code-forensics-stinger from legioncodeinc/vibe-coding-tools is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add legioncodeinc/vibe-coding-tools/code-forensics-stinger@git:20261013.b48795ePins git:20261013.b48795e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- legioncodeinc/vibe-coding-tools
- Path
plugins/code-audit-tools/skills/code-forensics-stinger/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261013.b48795e, committed Oct 13, 2026
- Size
- 3,674 bytes
- Repository stars
- 94
- License
- a license file GitHub does not identify
Review software vendor engagements using contracts, invoices, messages and delivery records. Produce cited evidence drafts for human or counsel review. Read README.md for the guide map.
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
# Code Forensics Stinger Use this skill when the user requests a forensic review of a software or agency engagement and can supply source records. Ask who the parties are and what happened. Never recognize a new matter by assuming a named party, country, price, jurisdiction or misconduct pattern from another matter. Read [README.md](README.md) and [principles](guides/00-principles.md) first. For routine code review, route to the relevant engineering specialist. Legal determinations belong to counsel. ## Workflow | Phase | Guide | Result | |---|---|---| | 0 | [Intake](guides/01-intake.md) | Agreed scope, materials and private case workspace | | 1 | [Email](guides/02-email-processing.md) | Source-indexed communication records | | 2 | [Invoices](guides/03-invoice-extrapolation.md) | Documented billing and separate estimates | | 3 | [Git](guides/04-git-log-forensics.md) | Acquired history with stated limits | | 4 | [Dependencies](guides/05-cve-research.md) | Version evidence and dated advisories | | 5 | [Logs](guides/06-audit-log-analysis.md) | Observed activity and coverage gaps | | 6 | [Marketing](guides/07-marketing-analysis.md) | Contracted outputs and comparable metrics | …
Read the whole file at its exact version.
How to install
mdr add legioncodeinc/vibe-coding-tools/code-forensics-stinger@sha256:45b1e216ab4a3348The line at the top of this page pins the label git:20261013.b48795e, 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_4ecr4w47ivn7g2lw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 13, 2026.
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 (3674 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
legioncodeinc/vibe-coding-tools · 94 stars · license a license file GitHub does not identify · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4ecr4w47ivn7g2lw GET https://markdownregistry.com/api/v1/resolve?ref=legioncodeinc/vibe-coding-tools/code-forensics-stinger GET https://markdownregistry.com/api/v1/blob/45b1e216ab4a3348690cca88d6d81b8335cd118b2c1ab4fff58b972bbfcd3042
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.