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.
npx agentmods add commands/srstomp/pokayokay/sdkgit clone --depth 1 https://github.com/srstomp/pokayokayWrote this? Show the measurements
A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.
[](https://agentmods.dev/commands/srstomp/pokayokay/sdk)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 | $0.00006 | $0.00575 |
| Opus 5 | $0.00003 | $0.00287 |
| Sonnet 5 | $0.00001 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
sdk 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDK Development Workflow
SDK task: $ARGUMENTS
Steps
1. Identify SDK Task Type
From $ARGUMENTS, determine:
- Create: Build new SDK for existing API
- Extract: Pull reusable code into SDK
- Publish: Release SDK to npm
- Update: Add features or fix issues
2. Design SDK Architecture
For Creation:
- Analyze API endpoints
- Design client interface
- Plan type definitions
- Choose HTTP client (fetch, axios)
For Extraction:
- Identify reusable code
- Define public API surface
- Plan breaking changes
- Design migration path
3. Implement SDK
Package Structure:
sdk/
├── src/
│ ├── index.ts # Public exports
│ ├── client.ts # API client
│ ├── types.ts # TypeScript types
│ └── errors.ts # Custom errors
├── package.json
├── tsconfig.json
└── README.md
Key Features:
- Full TypeScript types
- ESM and CJS builds
- Tree-shakeable exports
- Proper error handling
- Request/response interceptors
4. Build Configuration
{
"main": "./dist/index.cjs",
"module": "./dist/index.js",
"types": "./dist/index.d.ts",
"exports": {
".": {
"import": "./dist/index.js",
"require": "./dist/index.cjs",
"types": "./dist/index.d.ts"
}
}
}
5. Documentation
- Installation instructions
- Quick start example
- API reference
- Error handling guide
6. Create Implementation Tasks
npx @stevestomp/ohno-cli create "SDK: [specific task]" -t feature
Covers
- SDK architecture design
- TypeScript configuration
- Build setup (ESM/CJS)
- Type definitions
- Error handling patterns
- Documentation generation
- npm publishing
Related Commands
/pokayokay:api- Design underlying API/pokayokay:docs- SDK documentation/pokayokay:test- SDK testing strategy/pokayokay:work- Implement SDK
Skill Integration
When SDK work involves:
- API design → Also load
api-designskill - Documentation → Also load
documentationskill - Testing → Also load
testing-strategyskill
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.
- 3d ago First seen · 105 lines · 6 tokens per session scan A fc2a8b2b2013
sdk is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 575 once invoked, about $0.0000 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-31.
Other commands, from other repositories
build-fix
빌드 에러를 자동으로 분석하고 수정합니다.
test-ts
Run TypeScript tests for Solana frontends and Anchor programs.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
scaffold-react
Quickly scaffold a new React + TypeScript project with Claude Code configuration.
11-observability
MCP server that serves deterministic, enterprise-grade prompts for rewriting any Node.js project to production-quality TypeScript. Supports http-api, library, cli, worker, and mcp-server project types.
format
Auto-format code and fix TypeScript issues.