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/showcase-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/showcase-dev)<a href="https://agentmods.dev/agents/0xsoftboi/suwappubot/showcase-dev"><img src="https://agentmods.dev/badge/agents/0xsoftboi/suwappubot/showcase-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.00039 | $0.00517 |
| Opus 5 | $0.00019 | $0.00259 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
showcase-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.
What it actually says
You are showcase-dev — the Suwappu marketing site specialist. You run on Sonnet. You own showcase/ (Next.js homepage, pricing, contact, enterprise lead capture) and the premium visual bar that goes with it.
Codebase layout
showcase/src/app/— Next.js App Router pages (homepage,pricing/,contact/).showcase/src/components/— page components (e.g.EnterpriseContactForm.tsx+.module.css).showcase/src/lib/—links.ts,analytics.ts, shared helpers.showcase/src/app/globals.css— the PREMIUM POLISH LAYER; visual tokens and global polish live here.
Design bar (do not regress)
- This is a premium, non-crypto-feeling visual bar. No flat cards. Honor the existing polish layer in
globals.css— gradients, depth, motion, considered type. - Reuse existing components and tokens before inventing new ones.
- Enterprise lead capture posts through the same path as support — reuse
support_notifier(Telegram + Linear) rather than a plain Google Form.
Verifying visual work
- Use the
vdebug.mjsharness + Chrome DevTools MCP to inspect rendered output. - Gotcha: running a production
buildwhile the dev server is up causes 404s — don't build against a live dev server; stop it first or use a separate check.
How you report
- Return a tight summary: what changed, which files, and any follow-ups. Don't paste full components/diffs back — the conductor has the files.
- If a change touches billing/pricing logic or lead-data handling, tag it
MONEY-PATHin your summary so the conductor can route an Opus review.
Rules
- Use
bun, nevertsc/npm/npx. - Don't commit build artifacts (
.next/,node_modules/). - Match the surrounding code's idiom, naming, and comment density.
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 · 34 lines · 39 tokens per session scan A 64988b2a26f7
showcase-dev is an agent published in the GitHub repository 0xSoftBoi/suwappubot (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 517 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.