By Seezo-io
Official Seezo plugin for AI clients. Connects shared public skills to the Seezo MCP.
Start a Seezo security assessment on a markdown spec / design doc / RFC / plan BEFORE any implementation code is written, then inject the resulting risks into the main agent's context. MANDATORY AUTO-TRIGGER. Run the moment the user signals they're about to implement work described in a planning/design artifact. Triggers: "implement this plan", "let's build it", "start coding this", "ship this spec", "lgtm, proceed"; acceptance of an ExitPlanMode plan; the user pointing at a tech spec, RFC, PRD, ADR, one-pager, or any `.md` planning artifact under `docs/`, `specs/`, `plans/`, `design/`, `rfcs/`, or the repo root and asking to build against it. Do NOT write or edit implementation code until this skill has produced `.seezo/{assessment_id}.md` and that file is in context. Also runs on explicit request: "start assessment", "run a Seezo scan", "scan with seezo", "run a Seezo assessment", "check this spec with Seezo".
Validate that the implemented code addresses every risk and abuse case flagged by a prior `start-assessment`. Reads `.seezo/{assessment_id}.md`, walks the working tree, decides a verdict per risk (`pass` / `fail` / `unclear`) with evidence, writes `.seezo/{assessment_id}.validation.md`, and posts the summary back so the main agent can decide whether to ship. MANDATORY AUTO-TRIGGER. Run the moment the implementation pass for a Seezo-assessed spec is complete and before the work is declared done. Triggers include (but are not limited to): - "we're done", "implementation is complete", "ready to ship", "wrap this up", "ready for review", "PR is ready" - the user asking for a final review before merge - the assistant about to summarise a feature as finished while `.seezo/config.json` has an `active_assessment_id` Also runs on explicit request: "validate implementation", "run validate-implementation", "run seezo-validate", "validate against the Seezo assessment", "check the code against Seezo".
External network access
Connects to servers outside your machine
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Official Seezo plugin for AI clients. Connects shared agent skills to the remote Seezo MCP so Seezo security workflows are available from Claude Code, Codex, Cursor, GitHub Copilot / VS Code, and Gemini CLI.
Status: beta. APIs, skill names, and manifests may still change. Pin a tag in CI if you need stability.
| Client | Install guide |
|---|---|
| Claude Code | docs/install-claude.md |
| Codex | docs/install-codex.md |
| Cursor | docs/install-cursor.md |
| GitHub Copilot / VS Code | docs/install-copilot.md |
| Gemini CLI | docs/install-gemini.md |
start-assessment — start a Seezo assessment from a plan, spec, RFC, ADR, or design doc before implementation begins.validate-implementation — validate implemented code against a prior Seezo assessment before declaring work done.The skills are host-agnostic. They keep outputs evidence-led, avoid leaking customer data or proprietary rules, and use the Seezo MCP only when it is configured, authenticated, and relevant.
The committed MCP configs target the public Seezo endpoint:
https://app.seezo.io/mcp
The canonical plugin payload is a single source of truth under plugins/seezo/. Client-specific files at the repo root are thin adapters around it.
plugins/seezo/
.claude-plugin/plugin.json # Claude Code plugin manifest
.codex-plugin/plugin.json # Codex plugin manifest
.mcp.json # MCP server config (Claude Code + Codex)
skills/
start-assessment/SKILL.md
validate-implementation/SKILL.md
Adapters at the root:
| Path | Used by |
|---|---|
.claude-plugin/marketplace.json | Claude Code marketplace entry → plugins/seezo/ |
.agents/plugins/marketplace.json | Codex marketplace entry → plugins/seezo/ |
.cursor-plugin/plugin.json, .cursor-plugin/marketplace.json | Cursor |
.cursor/mcp.json, mcp.json | Cursor MCP discovery |
.vscode/mcp.json, .vscode/settings.json | GitHub Copilot / VS Code (MCP + skill location) |
gemini-extension.json, GEMINI.md | Gemini CLI |
MIT — see LICENSE.
npx claudepluginhub seezo-io/ai-plugin --plugin seezoHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Memory compression system for Claude Code - persist context across sessions