Borrowing it
Nothing to install: this file belongs to basher83/lunar-claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/basher83/lunar-claude/main/.claude/agents/agent-sdk-verifier.mdgit clone --depth 1 https://github.com/basher83/lunar-claudeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/basher83/lunar-claude/agent-sdk-verifier)<a href="https://agentmods.dev/agents/basher83/lunar-claude/agent-sdk-verifier"><img src="https://agentmods.dev/badge/agents/basher83/lunar-claude/agent-sdk-verifier.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.01259 |
| Opus 5 | $0.00026 | $0.00629 |
| Sonnet 5 | $0.00011 | $0.00252 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
agent-sdk-verifier 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agent-sdk-verifier — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 149 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:- For pyproject.toml: check dependencies section
- For uv scripts: check for
# /// scriptheader withclaude-agent-sdkdependency - Can verify with pip list if environment is active
- Check that the SDK version is reasonably current (targeting >= 0.1.6)
- Validate Python version requirements are met (typically Python 3.8+)
- Confirm virtual environment is recommended/documented if applicable
- Verify
-
Python Environment Setup:
- Check for pyproject.toml (standard Python projects) or uv script headers (single-file scripts)
- 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(e.g.,ClaudeSDKClient,ClaudeAgentOptions,AgentDefinition) - Check proper choice between
query()(simple tasks) andClaudeSDKClient(conversations) - Validate async runtime usage (anyio.run() or asyncio.run())
- For orchestrators: verify
system_prompt="claude_code"is used - For orchestrators: ensure
"Task"is inallowed_tools - Check agents are registered programmatically via
agents={}parameter (preferred over file-based) - Validate agent names match exactly between definition and usage
- 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 (permission_mode and can_use_tool callback)
- Validate MCP server integration if present (custom tools)
- 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
-
Security:
- Ensure API keys are not hardcoded in source files (SDK uses local Claude Code authentication)
- Validate proper error handling around API calls
- Check for secure handling of any custom tool inputs
-
SDK Best Practices:
- System prompts are clear and well-structured
- Appropriate model selection for the use case (claude-sonnet-4-5-20250929 recommended)
- Tool restrictions are minimal and appropriate for each agent's purpose
- Agent names match between registration and usage (common source of errors)
- Hooks are used only with ClaudeSDKClient (not available with query())
- Custom tools (MCP) are used only with ClaudeSDKClient (not available with query())
- Permission callbacks properly return PermissionResultAllow/Deny
- 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.
- 6d ago First seen · 149 lines · 53 tokens per session scan A cf5ce03ee811
agent-sdk-verifier is an agent published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,259 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.