Isms Audit Expert
davila7/claude-code-templates
Senior ISMS Audit Expert for internal and external information security management system auditing.
Run a third-party / vendor security review and assign a risk tier with required controls.
Install Vendor Security Review
$ npx skills add mohitagw15856/pm-claude-skills --skill vendor-security-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-security-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vendor-security-review .claude/skills/vendor-security-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vendor-security-review" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-security-review into .claude/skills/vendor-security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-security-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-security-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill vendor-security-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-security-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vendor-security-review .agents/skills/vendor-security-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vendor-security-review" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-security-review into .agents/skills/vendor-security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-security-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill vendor-security-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-security-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vendor-security-review .cursor/skills/vendor-security-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vendor-security-review" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-security-review into .cursor/skills/vendor-security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-security-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/vendor-security-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill vendor-security-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-security-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vendor-security-review .gemini/skills/vendor-security-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vendor-security-review" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-security-review into .gemini/skills/vendor-security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-security-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills vendor-security-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill vendor-security-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vendor-security-review .github/skills/vendor-security-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vendor-security-review" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-security-review into .github/skills/vendor-security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-security-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill vendor-security-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-security-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vendor-security-review .opencode/skills/vendor-security-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vendor-security-review" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-security-review into .opencode/skills/vendor-security-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-security-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vendor-security-review- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 487 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run a third-party / vendor security review and assign a risk tier with required controls.
- Asked to assess a vendors security
- SKILL.md covers Required Inputs, Output Format, Programmatic Helper and Quality Checks, plus 3 more sections
- Runs Python scripts from its folder; calls python3
- Run a third-party risk assessment
What it does
Vendor Security Review is an agent skill from mohitagw15856/pm-claude-skills. Run a third-party / vendor security review and assign a risk tier with required controls. Use when asked to assess a vendor's security, run a third-party risk assessment, complete a security questionnaire about a vendor, or decide what due diligence a new tool needs. Produces a vendor risk assessment — a data/access-driven risk tier, the questionnaire focus, required evidence (SOC 2, pen test, DPA), residual risk, and an approve/conditional/reject recommendation.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/vendor_risk.py`).
It sits in Security, covering Security review, SOC 2 and security compliance and Penetration testing. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to assess a vendors security
- Run a third-party risk assessment
- Complete a security questionnaire about a vendor
- Decide what due diligence a new tool needs
Example prompts
- “/vendor-security-review”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vendor Security Review loads about 1.1k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 487 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 487 words, ~1,080 tokens.
Download SKILL.mdSave it as
.claude/skills/vendor-security-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- vendor-security-review
- description
- Run a third-party / vendor security review and assign a risk tier with required controls. Use when asked to assess a vendor's security, run a third-party risk assessment, complete a security questionnaire about a vendor, or decide what due diligence a new tool needs. Produces a vendor risk assessment — a data/access-driven risk tier, the questionnaire focus, required evidence (SOC 2, pen test, DPA), residual risk, and an approve/conditional/reject recommendation.
Vendor Security Review Skill
You inherit the security posture of every vendor that touches your data — and the right level of scrutiny depends on what they touch, not on how big their logo is. This skill tiers a vendor by data sensitivity and access, scopes the diligence to that tier (so a low-risk tool isn't over-audited and a high-risk one isn't waved through), and lands on a defensible approve / conditional / reject call.
Required Inputs
Ask for these only if they aren't already provided:
- What the vendor does and the data they'll access (none / internal / customer PII / sensitive / regulated).
- Access level — no system access, limited, or privileged/admin to your environment.
- Criticality — would an outage or breach of this vendor materially hurt you?
- Evidence available — SOC 2 / ISO 27001 reports, pen-test summary, DPA, security questionnaire responses.
Output Format
Vendor Security Review: [vendor] — [service]
1. Risk tiering — the tier (Low / Medium / High / Critical) driven by data sensitivity × access × criticality, with the reasoning. The tier sets how much diligence is warranted.
2. Diligence scope — what to require at this tier: e.g. Low = self-attestation; High/Critical = SOC 2 Type II or ISO 27001, pen-test summary, DPA/sub-processor list, incident-response and breach-notification terms.
3. Findings — a table of assessed areas and status:
| Area | Expectation | Finding | Risk |
|---|---|---|---|
| Encryption | At rest + in transit | TLS + AES-256 | 🟢 |
| Compliance | SOC 2 Type II | Type I only | 🟡 |
| Sub-processors | Disclosed + DPA | Not disclosed | 🔴 |
4. Residual risk & recommendation — what's left after compensating controls, and a clear Approve / Approve with conditions / Reject with the conditions and a re-review date.
Programmatic Helper
scripts/vendor_risk.py (stdlib only) computes the risk tier and the baseline required evidence from
the vendor's data/access/criticality profile, so tiering is consistent across reviewers:
# vendor.json: {"name":"Acme","data_sensitivity":"customer_pii","access":"privileged","criticality":"high","certs":["soc2_type1"]}
python3 scripts/vendor_risk.py vendor.json
python3 scripts/vendor_risk.py vendor.json --jsonShow full SKILL.md (210 more words)Show less
Quality Checks
- The risk tier is driven by data sensitivity × access × criticality — not vendor size or reputation
- Diligence depth matches the tier (no rubber-stamping high-risk; no over-auditing low-risk)
- High/Critical vendors are required to provide independent evidence (SOC 2 Type II / ISO 27001 / pen test), not self-attestation
- A DPA + sub-processor disclosure is required where the vendor handles personal data
- The recommendation is explicit (approve / conditional / reject) with conditions and a re-review date
Anti-Patterns
- Do not size diligence by the vendor's brand — a small vendor with privileged access to PII outranks a famous one with none
- Do not accept a SOC 2 Type I as equivalent to Type II — Type I is a point-in-time design check, not operating effectiveness
- Do not skip the sub-processor question — your data may flow to fourth parties you never assessed
- Do not approve high-risk vendors on a promise — require evidence and bind it in the contract (DPA, breach notice SLA)
- Do not treat the review as one-and-done — set a re-review cadence tied to the tier
Based On
Third-party / vendor risk management practice — data-and-access-driven tiering, evidence-based diligence, and contractual risk transfer.
Example Trigger Phrases
- "Assess a vendor's security."
- "Run a third-party risk assessment."
- "Complete a security questionnaire about a vendor."
- "Decide what due diligence a new tool needs."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in skills/vendor-security-review of mohitagw15856/pm-claude-skills.
- SKILL.md
- scripts/vendor_risk.py
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Vendor Security Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vendor Security Review this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Isms Audit Expertdavila7/claude-code-templates | 33k | 1 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Senior Secopsalirezarezvani/claude-skills | 28k | 1 repos | ~4k | Automated safety check: Pass | MIT | |
| Infrastructure Compliance Auditorborghei/Claude-Skills | 891 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Find Cybersecurity Firmjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~3.7k | Automated safety check: Notes | MIT | |
| Strix Code Vulnerability Scanusestrix/strix | 68k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Senior Secops
alirezarezvani/claude-skills
Senior SecOps engineer skill for application security, vulnerability management, compliance verification, and secure development practices.
Infrastructure Compliance Auditor
borghei/Claude-Skills
Cross-framework infrastructure security audit across cloud, network, and CI/CD.
Find Cybersecurity Firm
jeremylongshore/tons-of-skills-marketplace
A skill your agent uses whenever the user wants to find, shortlist, vet, or enrich US cybersecurity firms — pen-testing/red team, security audits, vCISO, SOC 2 readiness, incident response, managed…
Strix Code Vulnerability Scan
usestrix/strix
Runs a Strix white-box security review that reads the source, then exploits what it finds in a sandbox so each reported issue has a proof-of-concept.
Code Audit
3stoneBrother/code-audit
Professional code security audit skill covering 55+ vulnerability types.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Vendor Security Review
What does Vendor Security Review do?
Run a third-party / vendor security review and assign a risk tier with required controls. Vendor Security Review is an agent skill from mohitagw15856/pm-claude-skills. Run a third-party / vendor security review and assign a risk tier with required controls.
When should I use Vendor Security Review?
Vendor Security Review fits situations like: asked to assess a vendors security; run a third-party risk assessment; complete a security questionnaire about a vendor; decide what due diligence a new tool needs.
How do I install Vendor Security Review in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill vendor-security-review -a claude-code`. Or copy the skill folder (skills/vendor-security-review in mohitagw15856/pm-claude-skills) into .claude/skills/vendor-security-review in your project. Claude Code loads it when a task matches its description.
How do I install Vendor Security Review in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill vendor-security-review -a codex`. Or copy the skill folder (skills/vendor-security-review in mohitagw15856/pm-claude-skills) into .agents/skills/vendor-security-review in your project. Codex loads it when a task matches its description.
Can I use Vendor Security Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill vendor-security-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vendor-security-review, .gemini/skills/vendor-security-review, .github/skills/vendor-security-review and .opencode/skills/vendor-security-review in your project.
What does Vendor Security Review need to run?
Going by SKILL.md and its folder, Vendor Security Review needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Vendor Security Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vendor Security Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Vendor Security Review use?
Vendor Security Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vendor Security Review use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vendor Security Review?
Skills that share tags, products or a category with Vendor Security Review: Isms Audit Expert (davila7/claude-code-templates, 33k stars), Senior Secops (alirezarezvani/claude-skills, 28k stars), Infrastructure Compliance Auditor (borghei/Claude-Skills, 891 stars) and Find Cybersecurity Firm (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vendor Security Review?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.