forensify SKILL.md skillB
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
forensify 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/forensify@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alexgreensh/repo-forensics
- Path
skills/forensify/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.0, committed Aug 25, 2026
- First version recorded
- Apr 6, 2026
- Size
- 9,972 bytes
- Repository stars
- 203
- License
- a license file GitHub does not identify
Cross-agent self-inspection of your AI-agent stack. Audits skills, MCP servers, hooks, plugins, commands, credentials, and memory files across Claude Code, Codex, OpenClaw, and NanoClaw. Produces a structured inventory and narrative briefing with cross-ecosystem risk analysis. Use when the user asks to audit their own setup, check what they have installed, review their agent stack security posture, or understand cross-tool interactions. Use when a user has accumulated skills/plugins/MCP…
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
# Forensify
The agent stack you have already installed is your biggest blind spot.
`repo-forensics` catches threats before install. Forensify tells you what
is already on this machine, across every agent framework, and where the
credential, injection, and auto-execution surfaces are right now.
## What makes this different
Every Codex user has `~/.codex/auth.json`. TruffleHog will tell you it
contains secrets. Forensify tells you its permissions are 0o644 (world-readable),
its auth_mode is apiKey (non-rotating, broad-scope), it has not been refreshed
in 47 days, AND OpenClaw's `models status` command is known to silently
overwrite it (openai/codex#54506). That cross-ecosystem stack interaction
finding is a class no existing credential scanner produces.
## How it works
Three stages, each a separate component:
**1. Inventory (zero-LLM, deterministic)**
The agent runs `{baseDir}/scripts/build_inventory.py`. It reads
`{baseDir}/config/ecosystem_roots.json`, detects which ecosystems are
installed, walks every surface (skills, MCP, hooks, plugins, commands,
memory, credentials), and emits a JSON inventory. No model calls. Every
…Read the whole file at its exact version.
How to install
mdr add alexgreensh/repo-forensics/forensify@sha256:b720b881657c2cfbThe line at the top of this page pins the label v1.0.0, 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_utoly4gj3vsmuzot)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 6, 2026 and Aug 25, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-25 | ef473e6 | 9,972 B | B | view · diff |
| v1.0.0 | 2026-07-25 | 46772e0 | 9,524 B | B | view · diff |
| v1.0.0 | 2026-06-06 | 2427acc | 9,522 B | B | view · diff |
| v1.0.0 | 2026-04-06 | e6e0c5c | 9,342 B | B | view · diff |
| v0.1.0 | 2026-04-06 | 8b8d3ce | 9,342 B | B | view |
Audit of the latest version
- fail: No instruction to read or print local credentials (matched: read credential values.** `auth.json`, `.env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9972 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 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_utoly4gj3vsmuzot GET https://markdownregistry.com/api/v1/resolve?ref=alexgreensh/repo-forensics/forensify GET https://markdownregistry.com/api/v1/blob/b720b881657c2cfb42b34d133913013b9e1b38071dc00af2f69a1c04e2e0d16b
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