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/fhenixprotocol/fhenix-toolkit/fhenix-testsnpx skills add FhenixProtocol/fhenix-toolkit --skill fhenix-testsgit clone --depth 1 https://github.com/FhenixProtocol/fhenix-toolkitWrote 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/fhenixprotocol/fhenix-toolkit/fhenix-tests)<a href="https://agentmods.dev/skills/fhenixprotocol/fhenix-toolkit/fhenix-tests"><img src="https://agentmods.dev/badge/skills/fhenixprotocol/fhenix-toolkit/fhenix-tests.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.00107 | $0.01360 |
| Opus 5 | $0.00053 | $0.00680 |
| Sonnet 5 | $0.00021 | $0.00272 |
| Haiku 4.5 | $0.00011 | $0.00136 |
Grade A, and why
fhenix-tests 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fhenix-tests — test confidential CoFHE contracts and dApps
You activate when the user is writing tests that exercise Fhenix-encrypted code: Foundry .t.sol files importing FHE.sol, Hardhat .test.ts files using @cofhe/sdk or the Hardhat plugin's mock environment, or any file under tests/contracts/.
The first decision: Foundry mocks or Hardhat plugin?
| Choice | Use when |
|---|---|
Foundry mocks (cofhe-mock-contracts) |
Pure-Solidity testing; fast iteration; no Node.js dependency; testing branchless logic, select/allowThis paths, encrypted state transitions. |
Hardhat plugin (@cofhe/hardhat-plugin) |
End-to-end with the SDK; tests the encrypt→tx→decrypt loop; tests frontend integration; covers the on-chain + off-chain split. |
You can use both in one project — Foundry for unit-level Solidity logic, Hardhat for E2E flows.
Decision tree: references/decision-trees.md.
Hard rules — never violate
-
Mock gas ≠ prod gas. Mock environments simulate gas costs that don't match the threshold network's actual costs. Always validate gas-sensitive code on a testnet before mainnet.
-
execute()is the one async terminator — don't poll. The legacy on-chainFHE.decrypt(ct)+getDecryptResultSafe(ct)poll loop is gone. All decrypt paths terminate onawait client.decryptFor*(...).execute(); in MOCK mode it resolves immediately, in TESTNET mode it takes seconds. Tests mustawaitproperly and use realistic timeouts. -
Seed
FHE.random*for determinism. Pass a non-zero seed to make tests reproducible. Seed=0 picks a system seed → flaky tests. -
Test the ACL path. For every encrypted op stored in state, assert that subsequent operations succeed (proving
allowThiswas called correctly). ForgottenallowThisis a silent class of bug. -
Test both arms of
FHE.select. Even when the encrypted condition picks one arm at runtime, both must be valid expressions. Force both branches in tests by varying inputs. -
Verify on-chain + off-chain pairing. E2E tests must exercise the decrypt-flow pairing matrix (
allowPublic↔withoutPermit, etc.). A test that uses one without the other is testing a non-existent code path.
What ships with it
9 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.
- references/concepts/foundry-mocks-setup.md 4.3 KB
- references/concepts/hardhat-plugin-setup.md 4.3 KB
- references/concepts/mock-vs-prod-divergence.md 2.7 KB
- references/concepts/testing-decrypt-flows.md 4.1 KB
- references/concepts/testing-encrypted-input.md 3.8 KB
- references/concepts/testing-multi-permit.md 5.3 KB
- references/decision-trees.md 2.2 KB
- references/hard-rules.md 3.3 KB
- references/lookup-recipes.md 2.8 KB
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 · 122 lines · 107 tokens per session scan A dfd3041f8a4e
fhenix-tests is a skill published in the GitHub repository FhenixProtocol/fhenix-toolkit (12 stars, last pushed 3mo ago), licensed MIT. It adds 107 tokens to every session and 1,360 once invoked, about $0.0005 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
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
testing
Writing or debugging tests, choosing unit vs integration style, Postgres/ClickHouse tests, regenerating ClickHouse test schema, or exporting test helpers from packages without pulling test code into production bundles.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
test-pyramid
Analyze the repo's unit and E2E tests and propose rebalancing toward a test pyramid — which E2E tests (or assertions inside them) can be covered by unit tests, which unit-level gaps genuinely need E2E coverage, and where coverage is duplicated. Use when the user asks about test pyramid, test rebalancing, "should this…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.