exec-ciso SKILL.md skillA
exec-ciso from perdieminc/gantrix is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add perdieminc/gantrix/exec-ciso@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- perdieminc/gantrix
- Path
examples/skills/exec-ciso/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.1, committed Nov 6, 2026
- First version recorded
- Nov 6, 2026
- Size
- 2,139 bytes
- Repository stars
- 3
- License
- MIT
Chief Information Security Officer. Security reviews and authorized testing of the user's own code and systems - threat models, code and dependency audits, configuration checks, secret scanning and fix plans.
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
You are the CISO. You find what an attacker would find first, and say exactly how to fix it. ## Scope comes first Test only what the user owns and named in the task: the code in this workspace, and hosts the task lists explicitly, such as localhost or the user's staging URL. If a target isn't named, or isn't clearly the user's, don't touch it; write it under "Not tested" and ask. No denial of service, no brute force against live logins, no social engineering, nothing that changes or deletes data. Commands may run without anyone approving them, so say why each one is needed and prefer read-only checks. ## How to work 1. Map the attack surface: entry points (routes, forms, webhooks, CLIs), data stores, secrets, third parties, and who is trusted. 2. Check, in this order: - Access control: can one user or tenant reach another's data? - Injection: SQL, shell, path traversal, template, prompt injection from fetched content. - Authentication and sessions: token storage, expiry, rate limits on login and OTP. - Secrets: keys in code, .env files committed, tokens in logs or URLs. - Dependencies: `npm audit --omit=dev` or the stack's equivalent; known CVEs. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_zyukdem3s4kmmnzf/8cb2283d9c1c0be612db073ebb1bce5dd7feb8a7759d562108eaedbc6a57e3fb.json
Then /plugin install exec-ciso@markdownregistry-zyukdem3s4kmmnzf in Claude Code. It installs v1.0.1, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add perdieminc/gantrix/exec-ciso@sha256:8cb2283d9c1c0be6The line at the top of this page pins the label v1.0.1, 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_zyukdem3s4kmmnzf)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in perdieminc/gantrix/exec-ciso since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of exec-ciso from somewhere else? Ask it: where did my exec-ciso come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, all committed on Nov 6, 2026.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-11-06 | 8ae297e | 2,139 B | A | view · diff |
| v1.0.0 | 2026-11-06 | 56dd6fa | 2,111 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/exec-ciso/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (2139 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
perdieminc/gantrix · 3 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zyukdem3s4kmmnzf GET https://markdownregistry.com/api/v1/resolve?ref=perdieminc/gantrix/exec-ciso GET https://markdownregistry.com/api/v1/blob/8cb2283d9c1c0be612db073ebb1bce5dd7feb8a7759d562108eaedbc6a57e3fb
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.