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 skills add pivyme/suiperpower --skill deploy-to-mainnetgit clone --depth 1 https://github.com/pivyme/suiperpowerWrote 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/skills/pivyme/suiperpower/deploy-to-mainnet)<a href="https://agentmods.dev/skills/pivyme/suiperpower/deploy-to-mainnet"><img src="https://agentmods.dev/badge/skills/pivyme/suiperpower/deploy-to-mainnet/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pivyme/suiperpower/deploy-to-mainnet"><img src="https://agentmods.dev/badge/skills/pivyme/suiperpower/deploy-to-mainnet.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.01975 |
| Opus 5 | $0.00022 | $0.00988 |
| Sonnet 5 | $0.00009 | $0.00395 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
deploy-to-mainnet 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 9d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preamble (run first)
# Suiperpower telemetry. Routes through the CLI so projects.json + Convex stay in sync.
# Silent on failure so the skill never blocks. Opt out: SUIPERPOWER_TELEMETRY=off.
#
# AGENT NOTE: when this skill finishes, run the matching completion command:
# suiperpower track deploy-to-mainnet ship completed
# Or use "failed" / "aborted" if it ended that way.
command -v suiperpower >/dev/null 2>&1 && suiperpower track deploy-to-mainnet ship started >/dev/null 2>&1 &
true
If TEL_PROMPTED is no, before doing real work, ask the user:
Help suiperpower get better. We track which skills get used and how long they take. No code, no file paths, no PII. Change anytime in
~/.suiperpower/config.json.A) Sure, anonymous B) No thanks
Write the answer to ~/.suiperpower/config.json telemetryTier field and create ~/.suiperpower/.telemetry-prompted. Then continue.
What this skill does
Runs the mainnet deploy with refusal gates in front of the publish step. The point is not to gatekeep, it is to surface the gates honestly so the user is not deploying to mainnet because they typed a command, but because they have done the work that mainnet implies.
If a gate is missing, the skill names what is missing and routes the user to the relevant skill. The user can override and proceed by typing the literal phrase the skill asks for, but the override is logged in deploy-context.md so it is on the record.
When to use it
- After the testnet deploy was exercised by a frontend or PTB and the relevant anti-slop skills have run.
- For a production launch the user is willing to defend.
When NOT to use it
- Pre-MVP, before there is a working testnet deploy.
- For experimental projects that should stay on testnet. Mainnet introduces real cost and real user expectations.
- If the user only wants a "label" of mainnet without the responsibility. Route to
validate-business-modelandretention-loopfirst.
If you activated this and the user actually wants something else, consult skills/SKILL_ROUTER.md and hand off.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 173 lines · 44 tokens per session scan A 2f5329026859
deploy-to-mainnet is a skill published in the GitHub repository pivyme/suiperpower (12 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,975 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 skills, from other repositories
tokenomist-fundraising-lookup
Look up fundraising rounds, investors, and valuation data for tokens. Use when finding who invested, at what valuation, or analyzing investor portfolios.
tokenomist-unlock-analysis
Analyze token unlock events — upcoming unlocks, historical events, and allocation breakdowns. Use when checking unlock impact on market cap or reviewing unlock schedules.
tokenomist-allocation-breakdown
Get the full allocation distribution for a token — who owns what and how much is locked vs unlocked. Use when analyzing supply distribution across team, investors, community, etc.
tokenomist-burn-buyback
Check token burn and buyback activity. Use when analyzing deflationary mechanisms — burns, buybacks, and net inflation.
tokenomist-emission-report
Get daily or weekly token emission data with allocation breakdowns. Use when analyzing token inflation, comparing emission rates, or understanding supply increases.
tokenomist-token-overview
Get a summary list of all tracked tokens with market data and supply info. Use when browsing tokens, comparing market caps, or finding which tokens have fundraising/burn/buyback data.