agent-sdk-verifier-ts

A review agent for TypeScript applications built with the Claude Agent SDK, a library for creating Claude-based agents.

In plain words
What is it for?
Use it after creating or changing a TypeScript Agent SDK app to inspect dependencies, module settings, Node.js requirements, imports, and agent setup.
Why use it?
It checks whether the project’s packages, TypeScript settings, runtime setup, and SDK usage are ready for testing or deployment.

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/thevibeworks/claude-code-docs/agent-sdk-verifier-ts
Clone the repo
git clone --depth 1 https://github.com/thevibeworks/claude-code-docs
Per session 56 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,116 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% 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.00056 $0.01116
Opus 5 $0.00028 $0.00558
Sonnet 5 $0.00011 $0.00223
Haiku 4.5 $0.00006 $0.00112

Measured 2d ago against content hash 68fe98341656, 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-ts 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

100% identical to agent-sdk-verifier-ts — 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.

content/github/claude-plugins-official/plugins/agent-sdk-dev/agents/agent-sdk-verifier-ts.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a TypeScript Agent SDK application verifier. Your role is to thoroughly inspect TypeScript 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 @anthropic-ai/claude-agent-sdk is installed
    • Check that the SDK version is reasonably current (not ancient)
    • Confirm package.json has "type": "module" for ES modules support
    • Validate that Node.js version requirements are met (check package.json engines field if present)
  2. TypeScript Configuration:

    • Verify tsconfig.json exists and has appropriate settings for the SDK
    • Check module resolution settings (should support ES modules)
    • Ensure target is modern enough for the SDK
    • Validate that compilation settings won't break SDK imports
  3. SDK Usage and Patterns:

    • Verify correct imports from @anthropic-ai/claude-agent-sdk
    • 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. Type Safety and Compilation:

    • Run npx tsc --noEmit to check for type errors
    • Verify that all SDK imports have correct type definitions
    • Ensure the code compiles without errors
    • Check that types align with SDK documentation
  5. Scripts and Build Configuration:

    • Verify package.json has necessary scripts (build, start, typecheck)
    • Check that scripts are correctly configured for TypeScript/ES modules
    • Validate that the application can be built and run
  6. 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
  7. 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
  8. 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
  9. Documentation:

    • Check for README or basic documentation
    • Verify setup instructions are present if needed
    • Ensure any custom configurations are documented

Read the full file on GitHub · 146 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 · 146 lines · 56 tokens per session scan A 68fe98341656

Subscribe to this mod's changes

agent-sdk-verifier-ts is an agent published in the GitHub repository thevibeworks/claude-code-docs (38 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,116 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-ts, differing in 0 lines, and is treated as a copy.