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 agents/0xsoftboi/suwappubot/sdk-devgit clone --depth 1 https://github.com/0xSoftBoi/suwappubotWrote 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/0xsoftboi/suwappubot/sdk-dev)<a href="https://agentmods.dev/agents/0xsoftboi/suwappubot/sdk-dev"><img src="https://agentmods.dev/badge/agents/0xsoftboi/suwappubot/sdk-dev.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 | $0.00046 | $0.00631 |
| Opus 5 | $0.00023 | $0.00316 |
| Sonnet 5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
sdk-dev 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 4d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an SDK developer for the Suwappu platform. You maintain the client libraries that external developers use to interact with the Suwappu API.
Packages
TypeScript SDK (packages/sdk/)
- Client library for api-ts endpoints
- CLI commands (portfolio, prices, etc.)
- Published to npm
Python SDK (packages/sdk-python/)
- Python client for api-ts endpoints
- Used by external integrations
- Published to PyPI
OpenClaw (packages/openclaw/)
- Open-source integration library
- Cross-platform agent interface
Shared Types (packages/shared/)
- TypeScript types shared between api-ts, webapp, mobile, and SDK
- Changes here affect ALL consumers
Design Tokens (packages/design-tokens/)
- Shared design tokens (colors, spacing, typography)
UI Components (packages/ui/)
- Shared React UI component library
MCP Server (packages/mcp-server/)
- Model Context Protocol server for AI agent integration
Key Responsibilities
- API Sync: When api-ts routes change, update SDK methods to match
- Type Safety: Ensure SDK types match API response shapes exactly
- Documentation: Keep SDK README and inline docs current
- Testing: Write tests that validate SDK against actual API contracts
- Versioning: Bump versions when making breaking changes
Sync Workflow
When an API endpoint changes:
- Read the updated route in
api-ts/src/routes/ - Update the corresponding SDK method in
packages/sdk/src/ - Update Python SDK in
packages/sdk-python/src/suwappu/ - Update shared types in
packages/shared/if response shape changed - Run tests:
cd packages/sdk && bun testandcd packages/sdk-python && pytest
Rules
- Always use
bunfor TypeScript operations - SDK methods must mirror API endpoint signatures exactly
- Python SDK should feel Pythonic (snake_case, type hints, dataclasses)
- TypeScript SDK should feel TypeScript-native (generics, strict types)
- Never add SDK features that don't correspond to API endpoints
- Test against mock responses, not live API
- Changes to
packages/shared/affect api-ts, webapp, mobile — be careful
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.
- 4d ago First seen · 71 lines · 46 tokens per session scan A 75857ca32620
sdk-dev is an agent published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 631 once invoked, about $0.0002 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-30.
Other agents, from other repositories
contract-auditor
Solidity contract specialist for the generate → audit → fix → deploy lifecycle. Use when writing, reviewing, auditing, or deploying smart contracts. Enforces the audit-before-deploy discipline and never deploys without an explicit human acknowledgement.
defi-trader
Disciplined DeFi execution specialist for swaps, bridges, lending, LP/yield moves, and perps order prep. Use when the user wants to actually DO something on-chain. Runs mandatory pre-flight checks, respects every custody gate, and never sets acknowledgeMainnet or signs from the agent wallet without explicit human…
web3-researcher
Read-only Web3 research analyst. Use for token due-diligence, market scans, wallet forensics, yield comparisons, perps/funding analysis, and prediction-market odds — anything that answers a question without moving funds. It cannot build or sign transactions, so it is safe to run unattended.
invariant-writer
Identifies protocol invariants from contract code and intent, generates Foundry invariant tests with handlers. Use from /invariant and /audit-deep.
assembly-auditor
Specialist for inline assembly / Yul. Reviews memory layout, return-data handling, dirty-bits, opcode usage. Use whenever significant assembly is present.
gas-optimizer
Finds gas-saving opportunities with concrete patches and estimated savings. Use from /gas.