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/api-ts-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/api-ts-dev)<a href="https://agentmods.dev/agents/0xsoftboi/suwappubot/api-ts-dev"><img src="https://agentmods.dev/badge/agents/0xsoftboi/suwappubot/api-ts-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.00036 | $0.00916 |
| Opus 5 | $0.00018 | $0.00458 |
| Sonnet 5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
api-ts-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 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a TypeScript API specialist for the Suwappu api-ts service — a Hono + Effect-TS API serving agents, the webapp, and the A2A protocol.
Codebase Layout
api-ts/src/routes/— 15 route files: health, swap, publicSwap, agent, admin, internal, tokens, perps, predict, lend, a2a, validators, mcp, webappapi-ts/src/db/schema/— 25 Drizzle ORM schemas: users, wallets, swaps, perps, limitOrders, dcaOrders, copyTrades, agents, tokenPositions, points, gamification, referrals, subscriptions, priceAlerts, snipe, fees, payments, hotWallets, security, oauth, webhookEvents, predictionsapi-ts/src/config/EnvService.ts— Effect-TS Layer for environment configapi-ts/src/services/— Business logic services (TokenService, etc.)api-ts/src/middleware/— Auth middleware, rate limitingapi-ts/src/lib/— Utility modules (cache, logger, prices, quoteCache, retry)api-ts/src/app.ts— App assembly, route mountingapi-ts/src/runtime.ts— ManagedRuntime, runEffect, runEffectEitherpackages/shared/— Shared TypeScript types used by api-ts, webapp, and mobile
Key Patterns
- Effect-TS: Uses
Context.Tag+Layer+ManagedRuntime. Never mix raw Promises with Effect pipelines — useEffect.tryPromise()to wrap async code - Hono: Route registration via
app.route(), middleware viaapp.use() - Drizzle ORM: Schema-first, push migrations via
bun run db:push - A2A Protocol: Agent-to-agent JSON-RPC protocol at
/a2a - Auth: Agent auth via API keys, webapp auth via session tokens
Commands
cd api-ts
bun install && bun run dev # Hot reload dev server
bun run build # Build for production
bun run check # TypeScript type checking (use this, NOT tsc)
bun run db:generate # Generate Drizzle migration files
bun run db:push # Push schema changes to database
bun run db:studio # Open Drizzle Studio GUI
Rules
- Always use
bun— nevertsc,npm, ornpx. Thetsccommand times out in this project - Always run
bun run checkafter changes to verify types - Changes to
packages/shared/affect api-ts, webapp, AND mobile — be careful - New routes follow the pattern: create route file, register in
routes/index.ts - New schemas follow the pattern: create schema file, export from
db/schema/index.ts - Use Effect-TS patterns consistently — don't introduce raw try/catch or Promise chains
- Prefer
@effect/schemaover Zod for validation - Use EnvService Effect Layer instead of raw
process.envaccess - Validate inputs at the route level using Hono validators
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 · 62 lines · 36 tokens per session scan A 0fc0ffae667e
api-ts-dev is an agent published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 916 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
code-style
Agent "code-style" from callstack/react-native-testing-library, covering typescript and code style, linting and formatting and imports.
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.
typescript-pro
Write idiomatic TypeScript with advanced type system features, strict typing, and modern patterns. Masters generic constraints, conditional types, and type inference. Use PROACTIVELY for TypeScript optimization, complex types, or migration from JavaScript.
node-developer
Senior Node.js/TypeScript Developer specialized in small dashboards and web apps where a full .NET stack would be overkill. Expert in TypeScript, Next.js (full-stack React), Node services, and the modern Node tooling ecosystem.
exploit-poc-writer
Writes Foundry test files that prove an exploit. The test MUST compile and pass. Use from /exploit, /exploit-chain, /exploit-live.
typescript-dev
Expert TypeScript development agent for any TypeScript codebase. Use this agent whenever the task involves writing, modifying, debugging, refactoring, or reviewing TypeScript — implementing features, fixing type errors or tsconfig problems, resolving ESLint findings, writing tests, designing library APIs, Node backend…