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.
git clone --depth 1 https://github.com/SummerSec/SumSec-SkillsWrote 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/summersec/sumsec-skills/agent-sdk-verifier-ts)<a href="https://agentmods.dev/agents/summersec/sumsec-skills/agent-sdk-verifier-ts"><img src="https://agentmods.dev/badge/agents/summersec/sumsec-skills/agent-sdk-verifier-ts.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.00056 | $0.01116 |
| Opus 5 | $0.00028 | $0.00558 |
| Sonnet 5 | $0.00011 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00112 |
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 7d 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-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.
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:
-
SDK Installation and Configuration:
- Verify
@anthropic-ai/claude-agent-sdkis 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)
- Verify
-
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
-
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
- Verify correct imports from
-
Type Safety and Compilation:
- Run
npx tsc --noEmitto 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
- Run
-
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
-
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 if needed
- Ensure any custom configurations are documented
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.
- 7d ago First seen · 146 lines · 56 tokens per session scan A 68fe98341656
agent-sdk-verifier-ts is an agent published in the GitHub repository SummerSec/SumSec-Skills (8 stars, last pushed 22d ago), licensed Apache-2.0. 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.
Other agents, from other repositories
duplicate-pr
You are a duplicate PR detection agent. When a PR is opened, your job is to search for potentially duplicate or related open PRs.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.