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 instructions/fhenixprotocol/fhenix-toolkit/claude-mdgit 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/instructions/fhenixprotocol/fhenix-toolkit/claude-md)<a href="https://agentmods.dev/instructions/fhenixprotocol/fhenix-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/fhenixprotocol/fhenix-toolkit/claude-md.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.01048 | $0.01048 |
| Opus 5 | $0.00524 | $0.00524 |
| Sonnet 5 | $0.00210 | $0.00210 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
fhenix-toolkit CLAUDE.md scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
This plugin **does not snapshot API surfaces.** When you need to know whether a specific function exists, what its current signature is, or what version a feature shipped in, **look it up live** — every skill's `referenc How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — fhenix-toolkit
This file is read by Claude Code when this plugin is loaded. It primes Claude on how the four fhenix-* skills behave together so they activate correctly without explicit invocation.
Activation map
The skills are designed to activate from file context — Claude shouldn't need to be told which one to use. Use this table only when the user asks "which skill handles X?" or when activation seems to be missing.
| Task | Skill | Trigger surface |
|---|---|---|
| Writing a confidential contract | fhenix-contracts |
Solidity file imports @fhenixprotocol/cofhe-contracts/FHE.sol; uses euint* / ebool / eaddress types |
| Encrypting inputs, decrypting outputs, managing permits in app code | fhenix-sdk |
TypeScript file imports @cofhe/sdk or any subpath (/adapters, /permits, /web, /node); hooks like useCofhe* |
| Reviewing or auditing FHE code | fhenix-review |
PR-review prompts ("audit this", "is this safe", "look over my FHE code"); gh pr view output; diffs touching FHE.sol or @cofhe/sdk |
| Writing tests for FHE code | fhenix-tests |
.test.ts / .t.sol files importing FHE.sol, @cofhe/sdk, @cofhe/hardhat-plugin, or @fhenixprotocol/cofhe-mock-contracts; files under tests/contracts/ |
How the skills work together
Skills are additive, not exclusive. A test file that imports both FHE.sol and @cofhe/sdk legitimately fires fhenix-contracts + fhenix-sdk + fhenix-tests. The skills are designed to layer cleanly:
fhenix-contractsandfhenix-sdkare authoring skills — they teach the right patterns.fhenix-reviewis an audit lens on top of the authoring skills. It activates when the task is review (PR diff, "is this safe"), not when writing fresh code.fhenix-testsis its own track — testing has different patterns (mocks vs plugin, deterministic seeds, multi-permit fixtures) that don't apply to authoring or review.- The
fhe-reviewersubagent is invoked byfhenix-review(or directly) for deep audit passes. Use it when the diff is >200 LOC of FHE code or the merge is security-sensitive.
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.
- 4d ago First seen · 59 lines · 1,048 tokens per session scan A 35c198fac313
fhenix-toolkit CLAUDE.md is an instructions file published in the GitHub repository FhenixProtocol/fhenix-toolkit (12 stars, last pushed 3mo ago), licensed MIT. It adds 1,048 tokens to every session, about $0.0052 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.