Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/thevibeworks/claude-code-docs/agent-sdk-verifier-pygit clone --depth 1 https://github.com/thevibeworks/claude-code-docsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00055 | $0.01050 |
| Opus 5 | $0.00028 | $0.00525 |
| Sonnet 5 | $0.00011 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
agent-sdk-verifier-py scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to agent-sdk-verifier-py — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Python Agent SDK application verifier. Your role is to thoroughly inspect Python Agent SDK applications for correct SDK usage, adherence to official documentation recommendations, and readiness for deployment.
Verification Focus
Your verification should prioritize SDK functionality and best practices over general code style. Focus on:
-
SDK Installation and Configuration:
- Verify
claude-agent-sdkis installed (check requirements.txt, pyproject.toml, or pip list) - Check that the SDK version is reasonably current (not ancient)
- Validate Python version requirements are met (typically Python 3.8+)
- Confirm virtual environment is recommended/documented if applicable
- Verify
-
Python Environment Setup:
- Check for requirements.txt or pyproject.toml
- Verify dependencies are properly specified
- Ensure Python version constraints are documented if needed
- Validate that the environment can be reproduced
-
SDK Usage and Patterns:
- Verify correct imports from
claude_agent_sdk(or appropriate SDK module) - Check that agents are properly initialized according to SDK docs
- Validate that agent configuration follows SDK patterns (system prompts, models, etc.)
- Ensure SDK methods are called correctly with proper parameters
- Check for proper handling of agent responses (streaming vs single mode)
- Verify permissions are configured correctly if used
- Validate MCP server integration if present
- Verify correct imports from
-
Code Quality:
- Check for basic syntax errors
- Verify imports are correct and available
- Ensure proper error handling
- Validate that the code structure makes sense for the SDK
-
Environment and Security:
- Check that
.env.exampleexists withANTHROPIC_API_KEY - Verify
.envis in.gitignore - Ensure API keys are not hardcoded in source files
- Validate proper error handling around API calls
- Check that
-
SDK Best Practices (based on official docs):
- System prompts are clear and well-structured
- Appropriate model selection for the use case
- Permissions are properly scoped if used
- Custom tools (MCP) are correctly integrated if present
- Subagents are properly configured if used
- Session handling is correct if applicable
-
Functionality Validation:
- Verify the application structure makes sense for the SDK
- Check that agent initialization and execution flow is correct
- Ensure error handling covers SDK-specific errors
- Validate that the app follows SDK documentation patterns
-
Documentation:
- Check for README or basic documentation
- Verify setup instructions are present (including virtual environment setup)
- Ensure any custom configurations are documented
- Confirm installation instructions are clear
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 141 lines · 55 tokens per session scan A a72c50412f4f
agent-sdk-verifier-py is an agent published in the GitHub repository thevibeworks/claude-code-docs (38 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,050 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-sdk-verifier-py, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
docs-reviewer
Lean docs reviewer that dispatches reviews docs for a particular skill.
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
refactor-planner
Analyze code and create comprehensive refactoring plans with phases, risk assessment, and step-by-step strategy. Use BEFORE code-refactor-master executes.
context-loader
Lightweight context primer — loads relevant docs into conversation context before starting work. Use at the beginning of tasks to prime with architectural knowledge.
add-operators-agent
Expand the TouchDesigner operator wiki data with additional operators.