oss-forensics SKILL.md skillA
oss-forensics from metaspartan/cybara is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add metaspartan/cybara/oss-forensics@git:20260703.247aff5Pins git:20260703.247aff5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- metaspartan/cybara
- Path
skills/oss-forensics/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260703.247aff5, committed Jul 3, 2026
- Size
- 2,695 bytes
- Repository stars
- 32
- License
- MIT
Investigate open-source repository compromise, deleted commits, force-pushes, suspicious releases, and supply-chain indicators with evidence IDs.
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
# OSS Forensics
Use this for defensive supply-chain investigations: suspicious commits, force-pushes, deleted releases, maintainer takeover concerns, leaked secrets, or package compromise.
## Guardrails
- Evidence first. Every claim needs an evidence ID such as `EV-0001`.
- Separate fact from hypothesis. Prefix unverified inferences with `[HYPOTHESIS]`.
- Do not run code from the investigated repository.
- Redact secrets in chat and reports.
- Double-check SHAs, URLs, package versions, and actor names against more than one source when possible.
## Evidence Store
Create a working directory outside the target repo:
```bash
INVESTIGATION="oss-forensics-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$INVESTIGATION"/{evidence,reports}
cd "$INVESTIGATION"
printf "# Evidence\n\n" > evidence/index.md
```
Evidence entry shape:
```text
EV-0001
Source: local git log
Time collected: <ISO timestamp>
Claim supported: <short claim>
Artifact: evidence/git-log.txt
Notes: <why it matters>
```
## Collection Plan
1. Extract targets:
- repo, package names, SHAs, actors, date range, releases, domains, URLs.
2. Local git source:
- `git clone --mirror` or normal clone.
…Read the whole file at its exact version.
How to install
mdr add metaspartan/cybara/oss-forensics@sha256:af855bb2e9445ffbThe line at the top of this page pins the label git:20260703.247aff5, 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_crn6hopx327dnpht)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 3, 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 (2695 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
metaspartan/cybara · 32 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_crn6hopx327dnpht GET https://markdownregistry.com/api/v1/resolve?ref=metaspartan/cybara/oss-forensics GET https://markdownregistry.com/api/v1/blob/af855bb2e9445ffbb04e570fff3a3ebaa468c88b6efc719ea368231d258a256e
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.