Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hiromaily/go-crypto-walletnpx agentmods add skills/hiromaily/go-crypto-wallet/docs-updateWrote 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/hiromaily/go-crypto-wallet/docs-update)<a href="https://agentmods.dev/skills/hiromaily/go-crypto-wallet/docs-update"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/docs-update/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hiromaily/go-crypto-wallet/docs-update"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/docs-update.svg" alt="Reviewed on agentmods" width="80" 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.00022 | $0.01213 |
| Opus 5 | $0.00011 | $0.00607 |
| Sonnet 5 | $0.00004 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
docs-update 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 9d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Update Workflow
Workflow for documentation changes with SSOT awareness.
Prerequisites
- Use
git-workflowSkill for branch, commit, and PR workflow. - Understand SSOT structure before editing any documentation.
SSOT Awareness
Critical: Before editing documentation, identify if the file is an SSOT or references one.
SSOT Locations
| Category | SSOT Location | Description |
|---|---|---|
| Agent behavior | AGENTS.md |
Entry point for all agents |
| Agent instruction design | docs/ai/design.md |
Command/Skill/Rule architecture |
| Label definitions | docs/guidelines/task-classification.md |
All label types and meanings |
| Label → Skill mapping | .claude/skills/label-context-mapping/ |
Operational routing |
| Coding conventions | docs/guidelines/coding-conventions.md |
Code style rules |
| Security rules | docs/guidelines/security.md |
Security requirements |
| Testing standards | docs/guidelines/testing.md |
Test requirements |
| Workflow | docs/guidelines/workflow.md |
Development workflow |
SSOT Rules
- If editing an SSOT file: Update carefully, as other files reference it
- If editing a non-SSOT file: Ensure it references the SSOT, don't duplicate information
- If information conflicts: The SSOT is authoritative; update the referencing file
Applicable Files
| Path | Type | Description |
|---|---|---|
AGENTS.md |
SSOT | Agent behavior entry point |
ARCHITECTURE.md |
SSOT | System architecture |
docs/guidelines/ |
SSOT | Project guidelines and standards |
docs/design/ |
Reference | Design documents |
docs/chains/ |
Reference | Chain-specific documentation |
docs/ai/task-contexts/ |
Context | Task-specific procedures |
internal/AGENTS.md |
Scoped SSOT | Internal package guidelines |
pkg/AGENTS.md |
Scoped SSOT | Public package guidelines |
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.
- 9d ago First seen · 178 lines · 22 tokens per session scan A aedf17768a94
docs-update is a skill published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 1,213 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
agent-wallet
Operate a non-custodial blockchain wallet on-chain (EVM and Bitcoin), no exchange or MetaMask. Create or import a wallet, balances, send native/ERC-20/BTC, swap tokens, compile/deploy/call Solidity. Trigger on wallet, crypto, ETH, BTC, ERC-20, token, send, transfer, swap, trade, Solidity, contract, on-chain, testnet…
agent-solidity
Write, audit and deploy Solidity smart contracts through a gated multi-step workflow (spec, threat model, design, implementation, in-process EVM proof, security audit, deployment), with a local EVM sandbox that needs no Foundry, Hardhat, anvil, node or funds. Trigger on Solidity, smart contract, .sol, ERC-20, ERC-721…
pqc-scan
Inventory the cryptography in a codebase that a quantum computer would break, and report what the scan could not read. Use when asked about post-quantum readiness, cryptographic inventory, a CBOM, or which algorithms a project signs with.
bytesagain-wallet-tracker
Crypto wallet analytics reference — address formats, on-chain analytics, transaction tracing, hardware wallets, and approval revocation.
agent-wallet
Operate a non-custodial blockchain wallet on-chain (EVM and Bitcoin), no exchange or MetaMask. Create or import a wallet, balances, send native/ERC-20/BTC, swap tokens, compile/deploy/call Solidity. Trigger on wallet, crypto, ETH, BTC, ERC-20, token, send, transfer, swap, trade, Solidity, contract, on-chain, testnet…
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.