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-trust-workflownpx skills add neus/network --skill neus-trust-workflowgit clone --depth 1 https://github.com/neus/networkWrote 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/neus/network/neus-trust-workflow)<a href="https://agentmods.dev/skills/neus/network/neus-trust-workflow"><img src="https://agentmods.dev/badge/skills/neus/network/neus-trust-workflow.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.00044 | $0.00772 |
| Opus 5 | $0.00022 | $0.00386 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
neus-trust-workflow 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 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.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NEUS Trust Workflow
Reuse existing proofs first. Run a new check only when needed. Summarize as NEUS Verify: Passed, Action needed, or Blocked. Never dump raw tool JSON.
Use this before an assistant runs sensitive tools or takes another verification-sensitive step. Answer simple questions directly.
When to use
- Before sensitive tools, spend, publish, secrets, or agent actions
- When the user asks for NEUS Verify, proofs, Vault, or Trusted Agent setup
- When acting as a registered profile agent in a project
Workflow
neus_contextonce per session. Prefer signed-in profile context; omit wallet fields on check/verify tools.- Profile agent:
neus_agent_mount(orneus mount <agentId> --apply <host>) for identity, permissions, skills, and context. - Trust before action:
neus_proofs_check→neus_verify_or_guide. When signed in, ownership checks continue withneus_verify. Share a browser link only when a tool returns one. - Agent:
neus_agent_link. If missing,neus_agent_create(usegeneratefor a dedicated key). Thenneus_agent_mount. - Proofs:
neus_proofs_getfor exact fields. - Vault:
neus_secret_list/neus_secret_create/neus_secret_revoke. - Reuse existing proofs via
neus_proofs_checkbefore creating new ones. When signed in,neus_contextreturns the current profile context; re-call it only after a profile change. - Summarize as NEUS Verify.
NEUS Verify format
Use the Passed / Action needed / Blocked guidance from neus_context. Never invent proof IDs, check IDs, or statuses.
NEUS Verify: Passed. Requirement satisfied. Proof on file. Next: Continue.
NEUS Verify: Action needed. Missing: <step>. Next: Complete the secure step, then retry.
NEUS Verify: Blocked. A required trust condition was not satisfied. Next: Do not continue until the check passes.
Hard rules
- Proofs stay off the chain unless the user asks for a blockchain record. Do not prompt for a wallet otherwise.
- Use proof IDs only from tool responses. Prefer “proof ID” / “portable proof” in user text.
- Store secrets only via
neus_secret_create. Confirm stored name + proof ID. Never paste tokens into chat. - Use live check IDs from
neus_context/neus_verifiers_catalog. Do not hardcode a second catalog.
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.
- 4d ago First seen · 57 lines · 44 tokens per session scan A 61072a87d7f7
neus-trust-workflow is a skill published in the GitHub repository neus/network (23 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 772 once invoked, about $0.0002 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
new-contract
Scaffold a new Solidity contract with test, Ignition module, and tasks following project patterns.
flaky-smoke-tests
Diagnose intermittent VS Code Electron smoke-test failures from the Azure DevOps Flaky Smoke Tests pipeline (definition 700). Covers finding failed iterations, downloading task logs and platform artifacts with Azure CLI, correlating cumulative runner logs, tracing the introducing commit, and queueing focused…
nemoclaw-contributor-plan-issue
Plan, refine, scope, or divide a NemoClaw GitHub issue into independently valuable capability slices before implementation. Use when a user asks to plan an issue, refine its scope, define acceptance evidence, break it down, split it, or identify the first capability slice. Ask which lifecycle stage they want when a…
system-prompts
Write system prompts, tool docs, and agent definitions. Project tag conventions + RFC 2119 keywords + dense compression. Use when authoring or editing any prompt the model reads.
building-emdash-site
Build and customize EmDash CMS sites on Astro. Use when creating pages, defining collections, writing seed files, querying content, rendering Portable Text, setting up menus/taxonomies/widgets, configuring deployment, or any task involving an EmDash-powered Astro site. Assumes basic Astro knowledge but provides all…
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.