agent-sdk-verifier-py

A reviewer for Python applications built with the Agent SDK, a software library for creating AI agents. It checks setup, dependencies, Python configuration, and use of the SDK.

In plain words
What is it for?
Use it after creating or changing a Python Agent SDK app to check its packages, Python requirements, imports, initialization, and documented setup.
Why use it?
It catches configuration and SDK-usage problems before the application is tested or deployed.

Agent

Install

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.

agentmods
npx agentmods add agents/ccplugins/awesome-claude-code-plugins/agent-sdk-verifier-py
Clone the repo
git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,059 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00055 $0.01059
Opus 5 $0.00028 $0.00530
Sonnet 5 $0.00011 $0.00212
Haiku 4.5 $0.00006 $0.00106

Measured 2d ago against content hash 1bcedce357a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

This is a copy

97% identical to agent-sdk-verifier-py — 1 line 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.

plugins/agent-sdk-dev/agents/agent-sdk-verifier-py.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 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:

  1. SDK Installation and Configuration:

    • Verify claude-agent-sdk is 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
  2. 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
  3. 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
  4. 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
  5. Environment and Security:

    • Check that .env.example exists with ANTHROPIC_API_KEY
    • Verify .env is in .gitignore
    • Ensure API keys are not hardcoded in source files
    • Validate proper error handling around API calls
  6. 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
  7. 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
  8. 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

Read the full file on GitHub · 142 lines

Changes

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.

  1. 2d ago First seen · 142 lines · 55 tokens per session scan A 1bcedce357a8

Subscribe to this mod's changes

agent-sdk-verifier-py is an agent published in the GitHub repository ccplugins/awesome-claude-code-plugins (929 stars, last pushed 20d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,059 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to agent-sdk-verifier-py, differing in 1 line, and is treated as a copy.

Related

Other agents, from other repositories

e2e-test-agent

E2E test agent for validation.

alex-feel/claude-code-toolbox · 13 tokens

confluence-fetcher

ユーザーが Confluence ページの情報取得を依頼したとき、または Confluence URL を言及したときに使用する。 Context: ユーザーが Confluence URL を共有 user: "https://example.atlassian.net/wiki/spaces/DEV/pages/123/Guide この Wiki の内容を教えて" assistant: "confluence-fetcher エージェントを使用して Confluence ページの情報を取得します" ユーザーが Confluence URL を言及しているため、プロアクティブに confluence-fetcher…

lc-semba-ryuichiro/semba-claude-plugins · 437 tokens

jira-fetcher

ユーザーが Jira 課題の情報取得を依頼したとき、または Jira URL を言及したときに使用する。 Context: ユーザーが Jira URL を共有 user: "https://example.atlassian.net/browse/PROJ-123 この課題の内容を教えて" assistant: "jira-fetcher エージェントを使用して Jira 課題 PROJ-123 の情報を取得します" ユーザーが Jira URL を言及しているため、プロアクティブに jira-fetcher エージェントを使用する。 Context: ユーザーが Jira 課題の取得を依頼 user: "PROJ-123…

lc-semba-ryuichiro/semba-claude-plugins · 443 tokens

image-optimizer

ユーザーが画像の WebP 変換や最適化を依頼したときに使用する。 Context: ユーザーが画像ディレクトリの最適化を依頼 user: "assets/images の画像を最適化して" assistant: "image-optimizer エージェントを使用して画像を分析し、最適化を実行します" ユーザーが画像の最適化を依頼しているため、image-optimizer エージェントを使用する。 Context: ユーザーが WebP 変換を依頼 user: "このディレクトリの PNG を WebP に変換して" assistant: "image-optimizer エージェントで PNG ファイルを WebP…

lc-semba-ryuichiro/semba-claude-plugins · 401 tokens

notion-workspace-architect

Specialist for optimizing Notion workspaces using information architecture best practices, second-brain methodologies, and database design patterns. Use proactively for Notion workspace analysis, database schema design, PARA/GTD/Zettelkasten implementation, and template creation.

memyselfandm/cconami · 56 tokens

program-manager

Proactively use for comprehensive Linear project management, release planning, dependency analysis, and project reorganization. Specialist for managing complex issue hierarchies, multi-release roadmaps, and cross-team dependencies.

memyselfandm/cconami · 42 tokens