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/integrategit clone --depth 1 https://github.com/srstomp/pokayokayWhat 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.00005 | $0.00555 |
| Opus 5 | $0.00003 | $0.00278 |
| Sonnet 5 | $0.00001 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
integrate 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Integration Workflow
Integrate with: $ARGUMENTS
Steps
1. Gather API Information
From $ARGUMENTS, identify:
- API documentation URL
- Authentication method (API key, OAuth, etc.)
- Rate limits
- Available endpoints
2. Analyze Integration Requirements
- Which endpoints do we need?
- What data transformations required?
- Error handling requirements
- Caching strategy
3. Design Integration
Client Architecture:
// api/[service]/client.ts
export class ServiceClient {
constructor(config: ServiceConfig) {}
// Typed methods for each endpoint
async getResource(id: string): Promise<Resource> {}
async createResource(data: CreateData): Promise<Resource> {}
}
Key Components:
- Typed client wrapper
- Request/response interceptors
- Error handling with retries
- Rate limit handling
- Response caching (if appropriate)
4. Handle Authentication
API Key:
headers: {
'Authorization': `Bearer ${process.env.SERVICE_API_KEY}`
}
OAuth 2.0:
- Token storage
- Refresh token flow
- Token expiration handling
5. Implement Error Handling
class ServiceError extends Error {
constructor(
message: string,
public code: string,
public status: number
) {
super(message);
}
}
6. Add Observability
- Log all external API calls
- Track latency metrics
- Alert on error rates
7. Create Implementation Tasks
npx @stevestomp/ohno-cli create "Integration: [service] [endpoint]" -t feature
Covers
- API client design
- Authentication patterns
- Error handling
- Rate limit management
- Response caching
- Type safety
- Testing strategies
Related Commands
/pokayokay:api- Design internal API for integration/pokayokay:test- Test integration/pokayokay:security- Review API security/pokayokay:observe- Monitor integration/pokayokay:work- Implement integration
Skill Integration
When integration work involves:
- API design → Also load
api-designskill - Security review → Also load
security-auditskill - Monitoring → Also load
observabilityskill - 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.
- 2d ago First seen · 108 lines · 5 tokens per session scan A 8acced16bd08
integrate is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 555 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.