@keryn/skills 1.2.1 installs 8 skills into a project for Claude Code (/<name>) and Codex ($<name>). Each runs the installed Keryn CLI or MCP server and adds no scanner logic. How to install them and what they change: the Keryn Skills guide. The skill sections on this page are generated from each skill’s SKILL.md.
Quickstart
Section titled “Quickstart”This runs with Node.js 20 or newer and nothing else. It previews the files, writes them into a new directory and lists what was written. /path/to/ stands for the directory you run it in.
mkdir demo-projectnpx --yes @keryn/skills --target demo-project --host both --dry-runDry run: /path/to/demo-projectwould create .agents/skills/keryn-review/SKILL.mdwould create .agents/skills/keryn-diff/SKILL.mdwould create .agents/skills/keryn-explain/SKILL.mdwould create .agents/skills/keryn-fix/SKILL.mdwould create .agents/skills/keryn-verify/SKILL.mdwould create .agents/skills/keryn-mcp-audit/SKILL.mdwould create .agents/skills/keryn-cloud/SKILL.mdwould create .agents/skills/keryn-attribution/SKILL.mdwould create .claude/skills/keryn-review/SKILL.mdwould create .claude/skills/keryn-diff/SKILL.mdwould create .claude/skills/keryn-explain/SKILL.mdwould create .claude/skills/keryn-fix/SKILL.mdwould create .claude/skills/keryn-verify/SKILL.mdwould create .claude/skills/keryn-mcp-audit/SKILL.mdwould create .claude/skills/keryn-cloud/SKILL.mdwould create .claude/skills/keryn-attribution/SKILL.mdNo agent settings, permission rules, global skills, or CLI installation were changed.npx --yes @keryn/skills --target demo-project --host bothProject skills: /path/to/demo-projectcreated .agents/skills/keryn-review/SKILL.mdcreated .agents/skills/keryn-diff/SKILL.mdcreated .agents/skills/keryn-explain/SKILL.mdcreated .agents/skills/keryn-fix/SKILL.mdcreated .agents/skills/keryn-verify/SKILL.mdcreated .agents/skills/keryn-mcp-audit/SKILL.mdcreated .agents/skills/keryn-cloud/SKILL.mdcreated .agents/skills/keryn-attribution/SKILL.mdcreated .claude/skills/keryn-review/SKILL.mdcreated .claude/skills/keryn-diff/SKILL.mdcreated .claude/skills/keryn-explain/SKILL.mdcreated .claude/skills/keryn-fix/SKILL.mdcreated .claude/skills/keryn-verify/SKILL.mdcreated .claude/skills/keryn-mcp-audit/SKILL.mdcreated .claude/skills/keryn-cloud/SKILL.mdcreated .claude/skills/keryn-attribution/SKILL.mdNo agent settings, permission rules, global skills, or CLI installation were changed.ls demo-project/.claude/skillskeryn-attributionkeryn-cloudkeryn-diffkeryn-explainkeryn-fixkeryn-mcp-auditkeryn-reviewkeryn-verifyThe skills are now in the project. To do anything they need the Keryn CLI, and keryn-cloud needs the Keryn MCP server (see Limits).
keryn-review
Section titled “keryn-review”Review a repository with the installed Keryn CLI and explain its findings, AI inventory, policy result, and measured coverage. Use for a requested Keryn security review; code changes require a fix task. Needs the keryn CLI (download from https://keryn.app/download after signing in, then keryn login). Reads the project; keryn-fix is the one that changes code.
keryn-diff
Section titled “keryn-diff”Compare Keryn security findings and AI components against an explicit Git or saved-result baseline for a change or CI review. Use when the user asks what security-relevant evidence changed. Needs the keryn CLI (download from https://keryn.app/download after signing in, then keryn login). Reads the project; keryn-fix is the one that changes code.
keryn-explain
Section titled “keryn-explain”Explain a specific Keryn rule or saved finding using its source location, trace, proof level, remediation, and limitations. Use when the user needs to understand why a finding matters or how to assess it. Needs the keryn CLI (download from https://keryn.app/download after signing in, then keryn login). Reads the project; keryn-fix is the one that changes code.
keryn-fix
Section titled “keryn-fix”Fix a specified Keryn finding in the user’s code and check the result with targeted tests and a comparable rescan. Use when a code change is requested, preserving concurrent work and the existing gate policy. Needs the keryn CLI (download from https://keryn.app/download after signing in, then keryn login). Reads the project; keryn-fix is the one that changes code.
keryn-verify
Section titled “keryn-verify”Verify a claimed Keryn security fix by comparing before/after evidence and running relevant checks, or verify an evidence bundle’s integrity. Use for an explicit verification request; do not equate a clean rescan with exploit reproduction. Needs the keryn CLI (download from https://keryn.app/download after signing in, then keryn login). Reads the project; keryn-fix is the one that changes code.
keryn-mcp-audit
Section titled “keryn-mcp-audit”Audit the MCP servers a project or this machine would start, judge a server’s tools for risk and poisoning, pin them and detect later changes. Use when the user asks whether an MCP server is safe to add or whether one changed. Needs the keryn CLI (download from https://keryn.app/download after signing in, then keryn login). Read-only unless the user asks to pin or wrap.
keryn-cloud
Section titled “keryn-cloud”Run and read Keryn Cloud scans of public addresses through the Keryn MCP server, within the organization’s credit. Use when the user asks for a hosted trust, AI-surface or MCP scan, or to check Keryn Cloud credit and results. Needs the Keryn MCP server (npm install -g @keryn/mcp) with KERYN_API_KEY set or a paired device (keryn-mcp pair).
keryn-attribution
Section titled “keryn-attribution”Find where AI coding tools are used in a repository and which commits declare them, with a confidence on every answer. Use when the user asks which AI tools a project uses, how much of its history declares AI involvement, or whether a commit or a file shows AI assistance. Needs the keryn CLI (download from https://keryn.app/download after signing in, then keryn login) and, for the commit signals, a git work tree. Reads file paths and commit metadata; sends nothing anywhere.
Limits
Section titled “Limits”- The package contains skill files and an installer. It contains no scanner. Every skill needs the Keryn CLI, which is not on npm, and
keryn-cloudneeds the Keryn MCP server with a credential. - The skills are for Claude Code and Codex. The installer writes no files for other agents.
- It installs into one existing project directory. There is no global install, and both
--targetand--hostare required. - It never overwrites. A skill file that differs from the packaged one is refused and nothing is written. There is no force option. An identical file is reported as unchanged.
- It does not edit
AGENTS.md,CLAUDE.md, settings, permission rules or hooks. - The skills have not been run end to end in a real Claude Code or Codex conversation.