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/trustless-ai/agent-sdk/update-ercnpx skills add trustless-ai/agent-sdk --skill update-ercgit clone --depth 1 https://github.com/trustless-ai/agent-sdkWrote 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/trustless-ai/agent-sdk/update-erc)<a href="https://agentmods.dev/skills/trustless-ai/agent-sdk/update-erc"><img src="https://agentmods.dev/badge/skills/trustless-ai/agent-sdk/update-erc.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.00058 | $0.02685 |
| Opus 5 | $0.00029 | $0.01342 |
| Sonnet 5 | $0.00012 | $0.00537 |
| Haiku 4.5 | $0.00006 | $0.00268 |
Grade A, and why
update-erc 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update ERC
Refresh SDK support for an ERC that agent-sdk already implements, after agent-ercs changed something about it. Like add-erc, the output has two layers:
- Layer 1 — contract wrappers:
client.ts/client.py - Layer 2 — pure recompute:
recompute.ts/recompute.py
Process
-
Determine what changed. If not specified, ask which ERC changed in
agent-ercs, and what changed (or point to the commit/PR). Check out the relevantagent-ercsref if it differs from what's currently checked out. -
Diff against what's implemented. Compare the current
agent-ercsinterface against the existing clients for all four languages. Check whether the recompute layer files exist:typescript/src/<category>/<ERCXXXX>/recompute.ts+ testpython/src/agent_sdk/<category>/<ercxxxx>/recompute.py+ testrust/core/src/<erc_lowercase>/recompute.rs(inline#[cfg(test)])go/<category>/<erc_lowercase>/recompute.go+recompute_test.go
If they're missing and the ERC has spec changes (or had recompute-able claims that were never extracted), flag that Layer 2 needs to be created.
-
Re-classify only if warranted. Re-run the recompute-to-verify classification (see
add-erc's step 3) only if the interface or semantics changed in a way that could affect the verdict. Otherwise, carry the existing verdict forward unchanged. -
Identify pure recompute functions (Layer 2). For each claim the ERC makes, determine whether it involves a deterministic computation reproducible off-chain as a pure function. This is SEPARATE from recompute-to-verify classification (step 3). See
add-erc's step 4 for the full methodology and examples.Read the conformance vectors at
/Users/shakku/code/recompute-kit/conformance/agent-flow.vectors.json— cross-reference thestepfield with the ERC's claims. Any new or changed pure recompute functions from the spec update should be reflected here.If the recompute layer files already exist, diff them against any spec changes to the ERC and update accordingly. If they're missing and the ERC has pure recompute claims, plan to generate them.
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 · 109 lines · 58 tokens per session scan A 74d39a4def04
update-erc is a skill published in the GitHub repository trustless-ai/agent-sdk (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,685 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-31.
Other skills, from other repositories
cross-sdk-parity
Keep TypeScript and Python SDK behavior, generated client usage, public API naming, and docs examples aligned. Use when a change affects both SDKs, when generated client pins move, when comparing TS/Python behavior, or when a backend API contract changed. Do not use for single-language internal-only changes.
gjc-sdk-author
Author trusted-local TypeScript and Python scripts that operate GJC sessions through the broker-bound CLI.
n8n-code-nodes-official
Use when the user reaches for a Code node, mentions writing JavaScript or Python in n8n, or any custom logic comes up in workflow design. Triggers on "Code node", "Code", "JavaScript", "Python", "custom logic", "transform data", "$input", "$json transformation", "loop in code", "write a function", or any time the…
honcho-integration
Integrate Honcho memory into existing Python or TypeScript codebases. Use when adding Honcho SDK, setting up peers, configuring sessions, and accessing Honcho's representation.
implement-type-annotations
Add comprehensive type hints to Python/TypeScript code to improve IDE support, catch errors early, and enable better AI code understanding.
regenerate-grpc-stubs
Regenerate Python + TypeScript gRPC stubs after editing proto files. Use when proto/.proto changes, imports from bindu.grpc.generated fail, CI reports generated-code drift, or HandleMessages calls fail with proto mismatch.