Public install surfaces for adding VerifiedX to an existing codebase through the smallest real capture/trigger seam.
This repo does not re-implement VerifiedX. It teaches coding agents how to:
- inspect a repo with
verifiedx verify - read the repo's actual capture/trigger layer shape
- choose the least invasive supported VerifiedX seam
- apply only the minimal patch for that seam
- validate that the app still works
Builders already have systems. VerifiedX should fit those systems in a few lines, not force them to redesign their product around a demo harness.
- Product and API keys: https://verifiedx.me
- Docs: https://docs.verifiedx.me
If an agent gets stuck, it should use docs.verifiedx.me and pick the specific SDK page that matches the repo instead of guessing.
- Agent Skills standard skills for install and audit flows
- Codex plugin packaging
- Claude Code custom marketplace packaging
- Cursor custom marketplace packaging
- TypeScript:
@verifiedx-core/sdk@0.1.18 - Python:
verifiedx==0.1.9
- Python SDK: https://docs.verifiedx.me/sdks/python
- TypeScript SDK: https://docs.verifiedx.me/sdks/typescript
- OpenAI Agents SDK: https://docs.verifiedx.me/sdks/openai-agents-sdk
- Claude Agent SDK: https://docs.verifiedx.me/sdks/claude-agent-sdk
- Vercel AI SDK: https://docs.verifiedx.me/sdks/vercel-ai
- LangGraph: https://docs.verifiedx.me/sdks/langgraph
- OpenAI direct: https://docs.verifiedx.me/sdks/openai
- Anthropic / Claude direct: https://docs.verifiedx.me/sdks/anthropic
- LangGraph (OpenAI): https://docs.verifiedx.me/sdks/langgraph-openai
- LangGraph (Anthropic / Claude): https://docs.verifiedx.me/sdks/langgraph-anthropic
- MCP Python: https://docs.verifiedx.me/sdks/mcp-python
- MCP TypeScript: https://docs.verifiedx.me/sdks/mcp-typescript
Use the framework-native adapter when the repo already runs through one:
- TypeScript OpenAI Agents
- TypeScript Claude Agent SDK
- TypeScript LangGraph
- TypeScript Vercel AI SDK
- TypeScript Anthropic direct
- TypeScript OpenAI direct
- Python LangGraph
- Python LangChain
- Python Claude Agent SDK
- Python OpenAI Agents
- Python Anthropic direct
- Python OpenAI direct
Provider-specialized LangGraph docs are also covered:
- OpenAI-backed graphs:
langgraph-openai - Anthropic-backed graphs:
langgraph-anthropic
Use the lower-seam runtime install when the repo mainly crosses trust boundaries through transport/runtime surfaces rather than a supported agent adapter:
- TypeScript startup install via
initVerifiedX()with lower-seam fallbacks - Python startup install via
init_verifiedx()plusinstall_runtime()
These paths cover real lower-level seams already in the SDKs, including HTTP, DB, queue, browser, cloud, and file-write interception where supported.
Use explicit wrapping when the repo exposes MCP tools or a custom harness and the cleanest seam is the specific action/memory/tool boundary itself:
- TypeScript
wrapMcpTool(),bindHarness(),wrapToolCall(),wrapMemoryWrite(),wrapActionExecute() - Python
wrap_tool_handler(),wrap_tool_definition(),bind_harness(),wrap_tool_call(),wrap_memory_write(),wrap_action_execute()
For custom harnesses, the skills repo now also points agents at the raw runtime details the public docs provide:
- lower-seam defaults already captured automatically
- explicit binding categories
llm,retrievals,actions,memories, andtools - schema and docstring metadata
- composed-system upstream context
- runtime blocked-result and receipt behavior
There are two different distribution paths in this repo:
skills.shinstalls the rawinstall-verifiedxandverify-verifiedxskills directly into supported coding agents such as Codex, Claude Code, Cursor, and others.- plugin marketplaces install a packaged
verifiedxplugin for Claude Code, Cursor, or Codex.
There is no separate third marketplace submission just for raw skills. The real cross-agent skills path is the skills CLI command below.
npx skills add bigkan8/verifiedx-agent-skillsThis installs the same two self-contained skills into the agents supported by the local skills CLI. Then tell the agent:
Install VerifiedX into this repo.
Use Cursor's plugin install flow with this repo as the source, then ask:
Install VerifiedX into this repo.
The packaged plugin lives in cursor/verifiedx.
Add this repo as a custom plugin marketplace, install the verifiedx plugin, then ask:
Install VerifiedX into this repo.
The packaged plugin lives in claude/verifiedx.
Install the skills from this repo or add the packaged Codex plugin, then ask:
Install VerifiedX into this repo.
The packaged plugin lives in plugins/verifiedx.
The install skill:
- runs
verifiedx verify --jsonor an ephemeralnpx @verifiedx-core/sdkprobe - reads the recommended integration kind and the detected capture/trigger layers
- installs the correct SDK package
- runs
verifiedx init --write - applies only the minimal code change for the detected seam
- re-runs verification and the repo's own quick validation
It does not:
- scaffold a new system
- ask the builder to enumerate guarded actions
- invent fallback lanes to make VerifiedX look good
- rewrite the product architecture
- downgrade a real lower-seam or explicit-wrapper integration just because the evals happened to use adapters
skills/: canonical Agent Skills source of truthplugins/verifiedx/: Codex plugin packagingclaude/verifiedx/: Claude Code plugin packagingcursor/verifiedx/: Cursor plugin packagingscripts/validate_repo.py: packaging validation
python scripts/validate_repo.py