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 skills/originprotocol/origin-dollar/smoke-testnpx skills add OriginProtocol/origin-dollar --skill smoke-testgit clone --depth 1 https://github.com/OriginProtocol/origin-dollarWrote 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/originprotocol/origin-dollar/smoke-test)<a href="https://agentmods.dev/skills/originprotocol/origin-dollar/smoke-test"><img src="https://agentmods.dev/badge/skills/originprotocol/origin-dollar/smoke-test.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.00024 | $0.03921 |
| Opus 5 | $0.00012 | $0.01961 |
| Sonnet 5 | $0.00005 | $0.00784 |
| Haiku 4.5 | $0.00002 | $0.00392 |
Grade A, and why
smoke-test 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 today.
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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smoke Test Skill
Generate Foundry smoke tests that verify deployment health by bootstrapping the actual deployed state (including pending governance actions) via the DeployManager/Resolver pipeline. Smoke tests sit between fork tests and production monitoring — they prove that a deployment is sound before governance execution. Follow the guidelines below to ensure consistency across the smoke test suite.
0. How Smoke Tests Differ from Unit and Fork Tests
| Aspect | Unit Tests | Fork Tests | Smoke Tests |
|---|---|---|---|
| State | Fresh deploys with mocks | Fresh deploys on top of fork | Actual deployed state via Resolver |
| Purpose | Full coverage, fuzz tests | Test specific integration paths | Verify deployment health |
| Contracts | Deployed in setUp |
Mix of fresh + forked | All resolved from DeployManager |
| Actors | makeAddr("Governor") |
makeAddr("Governor") |
ousd.governor() (from live contracts) |
| Tokens | MockERC20.mint() |
deal() cheatcode |
deal() cheatcode |
| Fuzz tests | Yes | No | No |
| Base class | Base |
BaseFork |
BaseSmoke (extends BaseFork) |
Key insight: Smoke tests answer "Is this deployment safe to execute?" — not "Does this code work?" (unit tests) or "Does this integrate correctly?" (fork tests).
1. Directory Layout
contracts/tests/smoke/<category>/<Product>/
├── shared/
│ └── Shared.t.sol # Abstract base with setUp, contract resolution, helpers
└── concrete/
├── ViewFunctions.t.sol # One file per feature area
├── Mint.t.sol
├── Redeem.t.sol
├── Transfer.t.sol
├── Rebasing.t.sol
└── YieldDelegation.t.sol
NEVER fuzz/ directory — smoke tests are concrete only (fork-based, same reason as fork tests).
One file per feature area, not per function. Group tests by what they verify. The feature groupings depend on the contract being tested:
- OTokens (OUSD, OETH, OSonic): ViewFunctions, Mint, Redeem, Transfer, Rebasing, YieldDelegation
- Vaults: Mint, Redeem, Rebase, Allocate, WithdrawalQueue
- Strategies: Deposit, Withdraw, Harvest, Rebalance
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.
- today First seen · 355 lines · 24 tokens per session scan A da8dae8bc41f
smoke-test is a skill published in the GitHub repository OriginProtocol/origin-dollar (151 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 3,921 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
web3-bug-classes
Complete reference for all 10 DeFi smart contract bug classes. Use this when hunting for specific vulnerability types, need attack patterns for accounting desync, access control, incomplete path, off-by-one, oracle manipulation, ERC4626 vaults, reentrancy, flash loans, signature replay, or proxy/upgrade bugs.
web3-methodology-research
External research synthesis from Trail of Bits, SlowMist, ConsenSys, Immunefi, and Cyfrin. Use this for advanced audit methodology, Echidna/Medusa fuzzing setup, Slither custom detector writing, attack pattern deep dives, or the 4-phase learning roadmap.
web3-poc-foundry
Complete Foundry PoC writing guide + all cheatcodes + DeFiHackLabs reproduction patterns. Use this when building a proof of concept exploit, setting up a fork test, using Foundry cheatcodes, or reproducing a known DeFi hack for learning.
web3-triage-report
Bug triage validation system, Immunefi report format, and 20 real paid bounty examples dissected. Use this when validating a finding before submitting, writing an Immunefi report, checking if a bug is actually valid, or studying real examples of paid vulnerabilities.