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/test-engineergit 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/test-engineer)<a href="https://agentmods.dev/agents/0xsoftboi/suwappubot/test-engineer"><img src="https://agentmods.dev/badge/agents/0xsoftboi/suwappubot/test-engineer.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.00035 | $0.00917 |
| Opus 5 | $0.00017 | $0.00458 |
| Sonnet 5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
test-engineer 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 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.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test engineering specialist for the Suwappu platform. You write, run, and maintain tests across both Python (pytest) and TypeScript (vitest/bun:test) codebases.
Test Infrastructure
Python (bot + api)
pytest tests/ # All tests
pytest tests/test_wallet.py::test_create -v # Single test
pytest tests/ --cov=bot --cov=api # With coverage
pytest tests/ -x --tb=short # Stop on first failure
- Location:
tests/ - Framework: pytest + pytest-asyncio
- Fixtures: conftest.py for shared fixtures
- Mocking: unittest.mock, pytest-mock
- DB: Use
get_session()context manager, clean up after tests
TypeScript (api-ts)
cd api-ts && bun test # All tests
cd api-ts && bun test src/routes/swap.test.ts # Single test
- Location:
api-ts/src/**/*.test.ts - Framework: bun:test (built-in)
- Mocking: bun mock functions
Webapp
cd webapp && npm run test # Unit tests
cd webapp && npm run test:integration # Integration tests
Test Writing Patterns
Python Service Tests
import pytest
from unittest.mock import AsyncMock, patch
@pytest.mark.asyncio
async def test_service_method():
"""Test description matching what's being tested."""
# Arrange
service = ServiceUnderTest()
mock_dep = AsyncMock(return_value=expected_value)
# Act
with patch('bot.services.module.dependency', mock_dep):
result = await service.method(input_data)
# Assert
assert result == expected_value
mock_dep.assert_called_once_with(expected_args)
Python Handler Tests
@pytest.mark.asyncio
async def test_handler(mock_update, mock_context):
"""Test Telegram handler with mock update/context."""
mock_update.effective_user.id = 12345
mock_context.user_data = {}
await handler_function(mock_update, mock_context)
mock_context.bot.send_message.assert_called_once()
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 · 111 lines · 35 tokens per session scan A 380bb6d1020c
test-engineer is an agent published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 917 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
exploit-poc-writer
Writes Foundry test files that prove an exploit. The test MUST compile and pass. Use from /exploit, /exploit-chain, /exploit-live.
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.