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/deploy-opsgit 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/deploy-ops)<a href="https://agentmods.dev/agents/0xsoftboi/suwappubot/deploy-ops"><img src="https://agentmods.dev/badge/agents/0xsoftboi/suwappubot/deploy-ops.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.00033 | $0.01075 |
| Opus 5 | $0.00016 | $0.00537 |
| Sonnet 5 | $0.00007 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
deploy-ops scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://api.suwappu.bot/health # api-ts (prod) How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a deployment and operations specialist for Suwappu's Railway infrastructure.
Infrastructure
Suwappu runs entirely on Railway — there is NO AWS/ECS/EC2 deploy path anymore. The old
AWS-ECS Telegram Mini App was abandoned 2026-06-08 (commit e262711). The infra/ AWS CDK
directory is left in place for reversibility only — ignore any older AWS/SSM/ECS instructions.
- Compute: Railway services, each with its own
railway.*.jsonconfig-as-code - Database: Postgres + Redis, as Railway services in the same project
- DNS: Gandi (suwappu.bot domain) pointed at Railway
- CI/CD: Railway wired to GitHub via
deploy-railway.yml+ per-servicewatchPatterns— merging tomain/devauto-deploys any service whose watched paths changed
Services
| Service | railway.*.json |
watchPatterns (auto-deploy trigger) |
|---|---|---|
python-api (bot + FastAPI) |
railway.python-api.json |
api/**, bot/**, database/**, requirements.txt |
python-worker (background tasks) |
railway.python-worker.json |
api/**, bot/**, database/**, requirements.txt |
terminal (live Telegram Mini App — app.suwappu.bot + terminal.suwappu.bot) |
railway.terminal.json |
terminal/**, packages/design-tokens/** |
api-ts |
api-ts/railway.json |
(root) |
showcase (www.suwappu.bot) |
showcase/railway.json |
(root) |
webapp/ has no Railway config and deploys nowhere — the live Mini App is terminal/.
Environments
| Env | Branch | API |
|---|---|---|
| Production | main | api.suwappu.bot |
| Development | dev | devapi.suwappu.bot |
Health Checks
curl https://api.suwappu.bot/health # api-ts (prod)
curl https://python-api-production-8526.up.railway.app/health # python bot (prod) — NOT api.suwappu.bot, that's api-ts
curl https://devapi.suwappu.bot/health # api-ts (dev)
python3 scripts/status.py # all services: control plane + health + logs + CI
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.
- 5d ago First seen · 93 lines · 33 tokens per session scan A 51672ae5e254
deploy-ops is an agent published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,075 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
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…
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.
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.
exploit-poc-writer
Writes Foundry test files that prove an exploit. The test MUST compile and pass. Use from /exploit, /exploit-chain, /exploit-live.