--- title: "Agent Sdk Verifier Ts: review, role & definition · Undominated.ai" canonical: https://undominated.ai/agents/anthropic-agent-sdk-verifier-ts/ description: "Checks a TypeScript Claude Agent SDK project against its configuration, current SDK guidance, type-checking results and environment-variable hygiene before a structured readiness report." --- # Agent Sdk Verifier Ts: review, role & definition · Undominated.ai > Checks a TypeScript Claude Agent SDK project against its configuration, current SDK guidance, type-checking results and environment-variable hygiene before a structured readiness report. [← Explore all agents](/agents/) AGENT DEVELOPMENT / anthropics # Agent Sdk Verifier Ts Checks a TypeScript Claude Agent SDK project against its configuration, current SDK guidance, type-checking results and environment-variable hygiene before a structured readiness report. Use this definition ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-21 Evidence 4 linked sources Publisher anthropics Licence Apache-2.0 ↗ Revision c447c3207a42 Read what was—and wasn’t—checked ↓ “Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for” anthropics · upstream description ↗ Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Checklist is SDK-specific: package name, "type":"module", engines, MCP/subagent/permissions patterns, ANTHROPIC_API_KEY in .env.example and .env gitignore. - Report schema separates critical runtime/security/type failures from documentation deviations and lists what not to nits-pick. ### A good fit for - After scaffolding or editing a TypeScript Claude Agent SDK app, checking install, tsconfig ESM, and key hygiene against the published TS SDK doc URL. - Producing a structured readiness report before someone else runs or deploys that app. ### Weigh up before choosing - No tool allowlist is declared, so documentation retrieval and shell execution use inherited host permissions. - Its type-checking command can require package resolution; use the project's installed toolchain and review network access before running it. - The report is a project and type-check review, not an executed agent-session, deployment or security certification. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - plugins/agent-sdk-dev/agents/agent-sdk-verifier-ts.md (complete frontmatter and body) - plugins/agent-sdk-dev/LICENSE (applicable redistribution terms) - README.md (host and installation guidance) - Host configuration documentation; immutable source and licence hashes ### Our findings - Frontmatter is only name, description, and model: sonnet—unlike the modernization agents, execution tools are entirely implicit. - Verification process step 2 says to Use WebFetch on https://docs.claude.com/en/api/agent-sdk/typescript; step 3 says Execute npx tsc --noEmit. Those are claimed runs, not declared tools. - Out of scope: formatting, type vs interface, unused-variable naming, general TS style unrelated to the SDK. - Security checks are file-pattern: .env.example with ANTHROPIC_API_KEY, .gitignore of .env, no hardcoded keys—not runtime secret scanning. - Functionality validation is structural (init/flow/error handling vs docs), not an executed agent session. ### Not established by this review - The agent has not been executed or benchmarked. - Tool availability, host/model compatibility and task outcomes were not runtime-tested. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Use the role in your project. Upstream setup instructions ↗ - Download the original agent-sdk-verifier-ts.md together with its LICENSE and attribution; inspect its instructions, model choice and tools. - For project use, place the definition in .claude/agents/agent-sdk-verifier-ts.md; the documented personal scope is ~/.claude/agents/. - Ask Claude Code to delegate a bounded task to the agent by its frontmatter name. Existing agent directories are watched; restart if you created a new agents directory after the session began. - Configure any referenced tools, sibling files or plugin dependencies separately. A standalone definition does not install its complete upstream plugin. ### Before you start - A TypeScript app using @anthropic-ai/claude-agent-sdk with package.json and tsconfig.json. - Network for docs fetch and possibly npx package resolution if those steps run. - TypeScript compiler available to the host for tsc --noEmit. - Official Agent SDK TypeScript documentation at the hardcoded URL remaining applicable. ### Compatibility Claude Code subagents ### Host-mediated repository and tool access - Requested in frontmatter: none (no tools list). Model pinned to sonnet. - Instructed in body: read package.json/tsconfig/src/.env.example/.gitignore; WebFetch official docs; run npx tsc --noEmit; optionally imply build/run. Instruction ≠ enforcement; inherited host tools may allow writes and network. ### Cost model Definition can be reused under its stated licence. Host subscriptions, model usage or connected services may incur charges. THE COMPLETE REVIEWED DEFINITION ## Read it before you reuse it. Original source bytes, with attribution. Review the host-specific setup notes above. Copy definition ↗ [Download definition + licence ↗](/resources/agents/anthropic-agent-sdk-verifier-ts/bundle.zip)[Raw Markdown ↗](/resources/agents/anthropic-agent-sdk-verifier-ts/definition.md) --- name: agent-sdk-verifier-ts description: Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified. model: sonnet --- 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 ## What NOT to Focus On - General code style preferences (formatting, naming conventions, etc.) - Whether developers use `type` vs `interface` or other TypeScript style choices - Unused variable naming conventions - General TypeScript best practices unrelated to SDK usage ## Verification Process 1. **Read the relevant files**: - package.json - tsconfig.json - Main application files (index.ts, src/\*, etc.) - .env.example and .gitignore - Any configuration files 2. **Check SDK Documentation Adherence**: - Use WebFetch to reference the official TypeScript SDK docs: https://docs.claude.com/en/api/agent-sdk/typescript - Compare the implementation against official patterns and recommendations - Note any deviations from documented best practices 3. **Run Type Checking**: - Execute `npx tsc --noEmit` to verify no type errors - Report any compilation issues 4. **Analyze SDK Usage**: - Verify SDK methods are used correctly - Check that configuration options match SDK documentation - Validate that patterns follow official examples ## Verification Report Format Provide a comprehensive report: **Overall Status**: PASS | PASS WITH WARNINGS | FAIL **Summary**: Brief overview of findings **Critical Issues** (if any): - Issues that prevent the app from functioning - Security problems - SDK usage errors that will cause runtime failures - Type errors or compilation failures **Warnings** (if any): - Suboptimal SDK usage patterns - Missing SDK features that would improve the app - Deviations from SDK documentation recommendations - Missing documentation **Passed Checks**: - What is correctly configured - SDK features properly implemented - Security measures in place **Recommendations**: - Specific suggestions for improvement - References to SDK documentation - Next steps for enhancement Be thorough but constructive. Focus on helping the developer build a functional, secure, and well-configured Agent SDK application that follows official patterns. The download contains agent-sdk-verifier-ts.md . Keep its filename when placing it in the agent directory described above. By **anthropics**. Exact upstream source ↗ · [Licence](/resources/agents/anthropic-agent-sdk-verifier-ts/LICENSE.txt) · [Attribution](/resources/agents/anthropic-agent-sdk-verifier-ts/ATTRIBUTION.txt) SHA-256 68fe98341656fa242a5de9272165481d62b5670b2fff294961bc45a5c4ee57ea Read the applicable licence Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - agent-sdk-verifier-ts — complete upstream definition ↗ Checked 2026-09-21 https://github.com/anthropics/claude-plugins-official/blob/c447c3207a425bc4e2a0d068435f64b0477ae981/plugins/agent-sdk-dev/agents/agent-sdk-verifier-ts.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access - Applicable upstream licence ↗ Checked 2026-09-21 https://github.com/anthropics/claude-plugins-official/blob/c447c3207a425bc4e2a0d068435f64b0477ae981/plugins/agent-sdk-dev/LICENSE Supports: license, artifact - Repository installation and scope guidance ↗ Checked 2026-09-21 https://github.com/anthropics/claude-plugins-official/blob/c447c3207a425bc4e2a0d068435f64b0477ae981/README.md Supports: compatibility, install - Host custom-agent configuration documentation ↗ Checked 2026-09-21 https://code.claude.com/docs/en/sub-agents.md Supports: compatibility, install, access, review, limitations KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Agent Memory Curator ↗ Maintains a confirmed agent memory store with dated facts, visible corrections and user-reviewed pruning proposals.](/agents/voltagent-memory-curator/)[### Agent-Log Knowledge Synthesizer ↗ Finds recurring patterns in an explicitly scoped set of agent logs and writes cited findings with counts derived from the actual files.](/agents/voltagent-knowledge-synthesizer/)[### Harness Optimizer ↗ Tunes agent configuration with an explicit evaluation definition, repeated trials, baseline checks and rollback instructions for failed experiments.](/agents/ecc-harness-optimizer/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)