repo-forensics SKILL.md skillC
repo-forensics from alexgreensh/repo-forensics is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alexgreensh/repo-forensics/repo-forensics@git:20261022.e590f5cPins git:20261022.e590f5c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- C, 15 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alexgreensh/repo-forensics
- Path
plugins/repo-forensics/skills/repo-forensics/SKILL.md- Versions recorded
- 10
- Latest version
- git:20261022.e590f5c, committed Oct 22, 2026
- First version recorded
- Aug 5, 2026
- Size
- 44,396 bytes
- Repository stars
- 203
- License
- a license file GitHub does not identify
Security forensics for git repos, AI skills, and MCP servers. Audits dependencies, detects prompt injection, credential theft, runtime dynamism, manifest drift, known CVEs, CISA KEV (actively exploited) vulns, and 2026 attack patterns. Not for fixing vulnerabilities or pentesting.
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
<!-- repo-forensics v2 | built by Alex Greenshpun | https://linkedin.com/in/alexgreensh --> # Repo Forensics v2 Deep security auditing for repositories, AI agent skills, and MCP servers. ## Highlights - **Rules-as-data** (v2.10): ~545 behavioral detection patterns live in versioned JSON rule packs (`data/rulepacks/*.json`), not compiled into source. Each rule carries a stable id, severity, confidence score, explanation, and embedded self-tests. Pack-driven scanners: secrets, SAST, skill threats, MCP security, runtime dynamism, and shared patterns. Algorithmic scanners (entropy, AST, DAST, git forensics, integrity, manifest drift, binary, lifecycle, dependencies, infra, devcontainer, post-incident, dataflow, entrypoint) remain code-driven; they do not receive feed updates. - **Signed daily rule-pack feed** (v2.10): New detection rules reach installed users without a code release. An Ed25519-signed bundle is fetched by the daily `refresh_threat_dbs.py` pipeline. Shipped packs always work offline; the feed only overlays when verified, schema-valid, and strictly newer than the last …
Read the whole file at its exact version.
How to install
mdr add alexgreensh/repo-forensics/repo-forensics@sha256:1be919b1f75d3567The line at the top of this page pins the label git:20261022.e590f5c, 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_7v5wszbh6k4oshvu)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 10 versions of this file, between Aug 5, 2026 and Oct 22, 2026, about one every 9 days. Its first recorded version is graded B and its latest C.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261022.e590f5c latest | 2026-10-22 | e590f5c | 44,396 B | C | view · diff |
| git:20261022.f8db5ad | 2026-10-22 | f8db5ad | 43,960 B | C | view · diff |
| git:20261022.2eba499 | 2026-10-22 | 2eba499 | 43,936 B | C | view · diff |
| git:20261022.b858aa8 | 2026-10-22 | b858aa8 | 41,967 B | C | view · diff |
| git:20261022.c0a2e0a | 2026-10-22 | c0a2e0a | 41,824 B | C | view · diff |
| git:20260927.af6a266 | 2026-09-27 | af6a266 | 39,855 B | C | view · diff |
| git:20260922.0746c28 | 2026-09-22 | 0746c28 | 39,854 B | C | view · diff |
| git:20260922.ec41a47 | 2026-09-22 | ec41a47 | 39,546 B | C | view · diff |
| git:20260825.ef473e6 | 2026-08-25 | ef473e6 | 39,102 B | C | view · diff |
| git:20260805.44252a6 | 2026-08-05 | 44252a6 | 34,487 B | B | view |
Audit of the latest version
- fail: No prompt-injection phrasing (matched: ignore previous instructions)
- fail: No curl or wget piped into a shell (matched: curl | bash)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (44396 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 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
alexgreensh/repo-forensics · 203 stars · license a license file GitHub does not identify · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7v5wszbh6k4oshvu GET https://markdownregistry.com/api/v1/resolve?ref=alexgreensh/repo-forensics/repo-forensics GET https://markdownregistry.com/api/v1/blob/1be919b1f75d35677f405f5076ae6599b3f5229cc54343172d73036171a9c77a
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 alexgreensh/repo-forensics
Every file in alexgreensh/repo-forensics