verify Skill
Verify harness changes end-to-end without docker — drive the real pinned CLI against a header-capturing stub server with the exact env resolveauthenv() produces. Published by anthropics in defending-code-reference-harness.
What is verify Skill?
Verify harness changes end-to-end without docker — drive the real pinned CLI against a header-capturing stub server with the exact env resolveauthenv() produces. Published by anthropics in defending-code-reference-harness. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Deployment
- Deployment use cases
Technical details
- Install or run with Copy skill directory
When to use verify Skill
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/defending-code-reference-harness
- Skill file: .claude/skills/verify/SKILL.md
What it does
Verify harness changes end-to-end without docker — drive the real pinned CLI against a header-capturing stub server with the exact env resolveauthenv() produces.
Skill instructions
Verifying harness changes on a docker-less host The pipeline's real surface is the in-container claude -p process and its outbound API requests. Without docker, drive the same pinned CLI binary directly with the env dict the harness would inject via docker -e. Recipe 1. Get the pinned CLI (version from harness/agentimage.py:CLAUDECODEVERSION): npm install --no-save @anthropic-ai/claude-code@<pin in a temp dir → binary at nodemodules/@anthropic-ai/claude-code/bin/claude.exe (the .exe name is the real native-binary entry on Linux too, filled in by the package's postinstall — not a Windows leftover). 2. Stub API server: a tiny HTTP server that appends each request's headers to a JSONL file and returns a 400 invalidrequesterror (non-retryable, so the CLI exits fast; exit=1 is expected). 3. Build the agent env exactly as the pipeline does: python3 -c "from harness.auth import resolveauthenv; ..." and dump to an export-lines file with shlex.quote (values contain newlines — NEVER pass via env
Explore related resources
Frequently asked questions
What is verify?
verify is a open-source AI agent skill with Copy skill directory. Verify harness changes end-to-end without docker — drive the real pinned CLI against a header-capturing stub server with the exact env resolveauthenv() produces.
Who is verify best for?
verify is best for reusing agent instructions, scripts, and references, deployment workflows.
How do I install verify?
Install or run verify using Copy skill directory. Check verify for the latest setup command.
Is verify actively maintained?
verify may need a closer maintenance check before production use.
Auto-fetched from GitHub.
