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 FhenixProtocol/fhenix-toolkit --skill fhenix-reviewgit 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-review)<a href="https://agentmods.dev/skills/fhenixprotocol/fhenix-toolkit/fhenix-review"><img src="https://agentmods.dev/badge/skills/fhenixprotocol/fhenix-toolkit/fhenix-review.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.1 | $0.00118 | $0.01178 |
| Opus 5 | $0.00059 | $0.00589 |
| Sonnet 5 | $0.00024 | $0.00236 |
| Haiku 4.5 | $0.00012 | $0.00118 |
Grade A, and why
fhenix-review 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 8d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fhenix-review — audit confidential code
This skill is for review contexts. The companion skills fhenix-contracts and fhenix-sdk already activate when editing FHE code; this one layers an audit lens on top of (or instead of) them when the task is review rather than authoring.
What to look for, in order
- ACL bugs — missing
FHE.allowThisafter a stored encrypted write; mismatched ACL pairing (e.g.,decryptForTx().withoutPermit()withoutallowPublic);allowSendergranted to an attacker-controlledmsg.senderfor someone else's handle. - Decrypt-flow mismatches —
decryptForViewused wheredecryptForTxis needed (or vice versa); legacyFHE.decrypt(...)/getDecryptResultSafe(...)references that should have been migrated to the SDK-mediated flow. - Plaintext leaks —
trivialEncrypt(literal)for secret values; plaintext values stored / emitted alongside their encrypted twins; revert paths that branch on what should be private. - Branching on
ebool—if (FHE.gt(...)),require(FHE.gt(...)),while (...)— must beFHE.select. - Confidentiality ≠ anonymity — the dApp claims privacy but leaks via gas patterns, event-fact, or tx graph.
- Encrypted approval / allowance — anywhere code tries to use ERC-20
approve/transferFromsemantics for ciphertexts. - Randomness sourcing —
FHE.randomEuintXXused where user-contributed entropy is required (auctions, gifts, fair shuffles). - Input validation —
InEuintXXaccepted without "Proof of Plaintext Input" where the protocol's invariants depend on the cleartext meeting bounds. - Permit hygiene —
expirationin milliseconds not seconds; stale per-cycle permits; sharing-permit JSONs leaked publicly. - Standards mixing — ERC20Confidential + FHERC20 + ERC-7984 interoperating in one app without an explicit wrapper.
Full catalog: references/gotchas.md.
Default review workflow
Walk the changed code in this order:
- Read the contracts. For each function:
- Trace every encrypted op → confirm
FHE.allowThis(result)if stored. - For each
allow*call → check the pairing matrix. - For each
FHE.decrypt→ confirm async handling on the read side. - For each
select→ confirm both arms are the same encrypted type and neither leaks.
- Trace every encrypted op → confirm
- Read the SDK callsites. For each
decryptForView/decryptForTx:- Pair with the on-chain
allow*for the same handle. - Confirm permit expiration is in seconds.
- Confirm error handling uses
CofheError, notResult<T>.
- Pair with the on-chain
- Read the events. Any plaintext leaked? Any event whose mere occurrence reveals private state?
- Check the threat model, even informally. What's the worst observer? What can they see (values, graph, timing, gas)?
What ships with it
8 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/confidentiality-vs-anonymity.md 2.0 KB
- references/concepts/pattern-leakage.md 2.5 KB
- references/concepts/proof-of-plaintext-input.md 2.1 KB
- references/concepts/reveal-labels.md 2.5 KB
- references/decision-trees.md 2.1 KB
- references/gotchas.md 10 KB
- references/lookup-recipes.md 2.5 KB
- references/security-checklist.md 3.9 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.
- 8d ago First seen · 66 lines · 118 tokens per session scan A 374fd3fddb48
fhenix-review is a skill published in the GitHub repository FhenixProtocol/fhenix-toolkit (12 stars, last pushed 3mo ago), licensed MIT. It adds 118 tokens to every session and 1,178 once invoked, about $0.0006 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…