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/neus/network/neus-integratenpx skills add neus/network --skill neus-integrategit clone --depth 1 https://github.com/neus/networkWhat 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.00056 | $0.01005 |
| Opus 5 | $0.00028 | $0.00502 |
| Sonnet 5 | $0.00011 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
neus-integrate 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 3d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate NEUS
Add proof-based access control to an app in four steps. The developer needs a gateId from neus.network and their framework name. Everything else is handled here.
Ask once
Before writing code, ask the developer:
- What framework? (Next.js, Vite/React, Express, other)
- Do you have a gate ID? If not, point them to neus.network → profile → Listings → Publish, then copy the
gateId.
Do not ask about NEUS architecture, verifier types, proof schemas, wallet setup, or credential choices. The gate handles all of that.
Install
npm install @neus/sdk
If the app uses React, also ensure react and react-dom are installed (peer deps).
Browser: gate the content
React (Next.js, Vite, CRA)
import { VerifyGate, ProofBadge } from '@neus/sdk/widgets';
function ProtectedPage() {
return (
<VerifyGate gateId="gate_your-app-name">
<ProtectedContent />
</VerifyGate>
);
}
VerifyGate checks for an existing proof, opens hosted sign-in on neus.network when a new one is needed, then renders the children. Wallet, passkey, and OAuth all happen on NEUS, not inside the app.
Optional: show proof status anywhere with <ProofBadge qHash={proof.qHash} />.
Non-React (redirect flow)
import { getHostedCheckoutUrl } from '@neus/sdk';
window.location.assign(
getHostedCheckoutUrl({
gateId: 'gate_your-app-name',
returnUrl: 'https://myapp.com/auth/callback',
}),
);
Read the proof ID (qHash) from the callback URL query string, then store it.
Server: confirm access
Before granting access or paying out, confirm the visitor still satisfies the gate. Every NEUS account has an address (passkey and OAuth included, no separate wallet required).
import { NeusClient } from '@neus/sdk';
const client = new NeusClient();
const result = await client.gateCheck({
gateId: 'gate_your-app-name',
address: user.accountAddress,
});
if (!result.data?.gate?.allRequiredSatisfied) {
// send the user back to VerifyGate or NEUS sign-in
}
What ships with it
1 file 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.
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.
- 3d ago First seen · 119 lines · 56 tokens per session scan A 8ae33e2096b2
neus-integrate is a skill published in the GitHub repository neus/network (23 stars, last pushed 3d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,005 once invoked, about $0.0003 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
agent-browser
Drive a real browser to inspect or interact with a web page or app — navigate, take screenshots, read console and network, fill simple forms — for verification tasks, not unattended automation.
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.
rational-buddhism
当用户问某主张/玄学/灵修该不该信、想建立自己的验证标准、或寻找科学与精神的结合点时调用。 核心理念: 尝试一切, 亲自测试, 保持怀疑, 保留有用的, 舍弃没用的; 不可证伪的主张不进入基本真理; 冥想/接纳等内在技术可保留。 不适用于: 需要信仰安慰的临终/哀伤场景(尊重个体选择)。 Triggers: 该不该信/玄学/灵修/冥想/可证伪/验证/理性/rational buddhism/verify/belief.
workflow
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use…
verification-strategy
Thorough verification of completed work before declaring done.
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.