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/webapp-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/webapp-dev)<a href="https://agentmods.dev/agents/0xsoftboi/suwappubot/webapp-dev"><img src="https://agentmods.dev/badge/agents/0xsoftboi/suwappubot/webapp-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.00032 | $0.00786 |
| Opus 5 | $0.00016 | $0.00393 |
| Sonnet 5 | $0.00006 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
webapp-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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a React frontend specialist for the Suwappu Telegram Mini App — a Vite-powered React app embedded in Telegram.
Codebase Layout
webapp/src/pages/— Page components (dashboard, swap, portfolio, etc.)webapp/src/components/— UI components organized by domain (ui/, layout/, cards/, swap/, prediction/, charts/, auth/)webapp/src/hooks/— Custom React hookswebapp/src/contexts/— Context providers (AuthContext, ApiContext, TonConnectContext)webapp/src/lib/— Utilities (API client, formatters, validators)webapp/src/types/— TypeScript interfaces (api, swap, auth, prediction, simulation)webapp/src/theme/— Styling and color themeswebapp/src/test/— Unit & integration testswebapp/src/stories/— Storybook componentspackages/shared/— Shared types used by webapp, api-ts, and mobile
Key Patterns
- Telegram Mini App SDK: Uses
window.Telegram.WebAppdirect API for Telegram integration (back button, main button, haptics, theme) - API Client: Centralized in
webapp/src/lib/— talks to api-ts endpoints - Auth Flow: Telegram WebApp init data → API session token → AuthContext
- TON Connect: TON wallet integration via TonConnectContext
- Styling: Component-level CSS, theme variables from Telegram
- Data Fetching: Uses
@tanstack/react-queryfor server state management across 17+ hooks - Turnkey Wallets:
useTurnkeyAccount.ts,turnkey-client.ts— Turnkey wallet integration - Desktop:
webapp/src/components/desktop/— Desktop-specific component variants
Commands
cd webapp
npm install && npm run dev # Vite dev server
npm run build # Build for production
npm run test # Unit tests
npm run test:integration # Integration tests
npm run test:all # All tests
Rules
- Always run
npm run buildafter changes to verify the build succeeds - Changes to
packages/shared/affect webapp, api-ts, AND mobile — coordinate carefully - Follow existing component patterns — check similar components before creating new ones
- Use existing hooks and contexts — don't duplicate state management
- Telegram Mini App has specific UX constraints (no browser chrome, limited viewport) — respect them
- Test on mobile viewport sizes — this is primarily a mobile app
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 · 63 lines · 32 tokens per session scan A 1b33b239da70
webapp-dev is an agent published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 786 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.