Borrowing it
Nothing to install: this file belongs to OriginProtocol/origin-dollar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/OriginProtocol/origin-dollar/master/.claude/skills/unit-test/SKILL.mdgit 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/unit-test)<a href="https://agentmods.dev/skills/originprotocol/origin-dollar/unit-test"><img src="https://agentmods.dev/badge/skills/originprotocol/origin-dollar/unit-test/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/originprotocol/origin-dollar/unit-test"><img src="https://agentmods.dev/badge/skills/originprotocol/origin-dollar/unit-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.04577 |
| Opus 5.5 | $0.00008 | $0.01831 |
| Sonnet 5.5 | $0.00004 | $0.00915 |
| Haiku 4.5 | $0.00002 | $0.00458 |
Grade A, and why
unit-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 12d 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unit Test Skill
Generate Foundry unit tests for a specific contract, adhering to our established directory structure, naming conventions, and best practices. The tests should include both concrete scenarios and property-based fuzz tests, with clear organization and comprehensive coverage. Follow the guidelines below to ensure consistency and maintainability across our test suite.
1. Directory Layout
contracts/tests/unit/<category>/<ContractName>/
├── shared/
│ └── Shared.sol # Abstract base with setUp, mocks, helpers
├── concrete/
│ ├── FunctionA.t.sol # One file per public/external function
│ ├── FunctionB.t.sol
│ └── ViewFunctions.t.sol # Exception: all view/pure functions grouped in one file
└── fuzz/
├── FunctionA.fuzz.t.sol # Property-based tests per function
└── FunctionB.fuzz.t.sol
<category> matches the subdirectories already in contracts/tests/unit/ (vault, token, strategies, oracle, etc.).
One file per function rule
Each public/external state-changing function gets its own dedicated test file, named after the function in PascalCase (e.g. rebaseOptIn() → RebaseOptIn.t.sol, delegateYield() → DelegateYield.t.sol).
Exceptions (may be grouped into a single file):
- View/pure functions → group in
ViewFunctions.t.sol - Setter functions (governor/admin config) → group in
Admin.t.solorConfig.t.sol
Do NOT group multiple distinct functions in one file just because they are thematically related. For example, rebaseOptIn() and rebaseOptOut() are two separate functions and must have two separate files, even though they are conceptually related.
2. Inheritance Chain
forge-std/Test
└─ Base (contracts/tests/Base.sol) — actors, constants, external token refs
└─ Unit_Shared_Test (shared/Shared.sol) — abstract; setUp, deploy, helpers
├─ Unit_Concrete_<Contract>_<Feature>_Test (concrete/*.t.sol)
└─ Unit_Fuzz_<Contract>_<Feature>_Test (fuzz/*.fuzz.t.sol)
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.
- 12d ago Changed · -2 lines bcd694a17f0c
- 1mo ago First seen · 398 lines · 21 tokens per session scan A a574b65bbc64
unit-test is a skill published in the GitHub repository OriginProtocol/origin-dollar (153 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 4,577 once invoked, about $0.0001 per session on Opus 5.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
foundry-testing
Write and debug Foundry tests and Solidity scripts. Use when writing unit, fuzz, fork, or invariant tests, writing bulloak BTT .tree specs (Branching Tree Technique), using cheatcodes, benchmarking gas, measuring coverage, writing deploy scripts, or working in tests/ or script/.
verification-protocol
How to prove a hypothesis is TRUE or FALSE using Move unit tests.
fuzzer
This skill defines how to extract invariants from smart contracts and generate Foundry fuzz tests to verify them.
playground
Interactively test any ChainGPT API endpoint. Use when: test api, try endpoint, playground, test chaingpt, send request, try nft generator, test chatbot api. Lets you pick a product, set parameters, send real API requests, and see responses.
solidity-testing
Every core function must have tests covering.
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.