Borrowing it
Nothing to install: this file belongs to emercoin/emer-ai-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/emercoin/emer-ai-tools/main/.claude/skills/emercoin-identity/SKILL.mdgit clone --depth 1 https://github.com/emercoin/emer-ai-toolsWrote 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/emercoin/emer-ai-tools/emercoin-identity)<a href="https://agentmods.dev/skills/emercoin/emer-ai-tools/emercoin-identity"><img src="https://agentmods.dev/badge/skills/emercoin/emer-ai-tools/emercoin-identity/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/emercoin/emer-ai-tools/emercoin-identity"><img src="https://agentmods.dev/badge/skills/emercoin/emer-ai-tools/emercoin-identity.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.00072 | $0.01067 |
| Opus 5 | $0.00036 | $0.00534 |
| Sonnet 5 | $0.00014 | $0.00213 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
emercoin-identity 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 12d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Emercoin on-chain identity & memory for agents
This project (emer-ai-tools) exposes the Emercoin blockchain as an identity +
memory layer for AI agents through the emercoin-agent MCP server. Agents
need no cryptocurrency — the gateway's hot-wallet pays for every record.
Read AGENTS.md for the full rationale and trust model. This skill is the
operational checklist for using the tools.
When to use
- An agent wants a durable, verifiable identity → register an identity record.
- An agent wants to remember something (research result, document, prior memory) in a tamper-evident way → store its hash on-chain (keep the body off-chain).
- You need to look up an agent's identity or a stored record → read it back.
Prerequisites
The MCP server must be configured (see AGENTS.md → Quickstart). It needs the
gateway reachable at GATEWAY_URL. Auth is a session JWT obtained with the
device-flow login() + login_poll(), or a pre-set GATEWAY_JWT env var.
Tools (emercoin-agent MCP)
| Tool | Use it to |
|---|---|
node_status() |
check the node is synced before relying on reads |
login() + login_poll(session_id) |
get a session JWT via GitHub device flow (GitHub identity = root of trust) |
register_identity(address, metadata?) |
create/refresh this agent's ai:gh:<id> record |
store_memory(content_hash, metadata?) |
record one memory/research hash |
store_memory_batch(records) |
record many hashes in ONE atomic transaction |
read_record(name) |
read any record by NVS name |
Standard flows
1. Establish identity (once)
login()→ show the returneduser_code+verification_urito the user; after they authorize on GitHub,login_poll(<session_id>)caches the JWT.- Obtain an Emercoin address as the agent's signing key (the operator funds / manages the gateway wallet; for a self-sovereign key, generate one and supply its address). You can register first and add/rotate the address later.
register_identity(<address>, {"role": "...", "model": "..."}). This writesai:gh:<github_id>binding the GitHub id ↔ address on-chain. Re-registering with a new address rotates the key (same record, value update).
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.
- 12d ago First seen · 81 lines · 72 tokens per session scan A 2da9f34daca6
emercoin-identity is a skill published in the GitHub repository emercoin/emer-ai-tools (8 stars, last pushed 8d ago), licensed MIT. It adds 72 tokens to every session and 1,067 once invoked, about $0.0004 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
chainaware-behavioral-prediction
Use this skill whenever a user asks about wallet safety, fraud risk, rug pull detection, wallet behavior analysis, DeFi personalization, on-chain reputation scoring, AML checks, token ranking by holder quality, airdrop screening, lending risk, token launch auditing, or AI agent trust scoring. Triggers on questions…
chainstack
Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status, searching Chainstack docs, contacting the Chainstack team, or interacting with the Chainstack platform API via…
klever-dev
End-to-end Klever blockchain development — smart contracts (Rust/WASM), transaction building (@klever/connect, klever-go-sdk), deployment via ksc + koperator, and on-chain interaction via MCP tools. Use when the task involves KLV, KDA tokens, klv1 addresses, Klever smart contracts, or Klever node/API interaction.
sora-taira-testnet
Work against the SORA Taira testnet through its deployed Torii MCP endpoint for live account, asset, alias, contract, governance, Musubi package-registry, and transaction workflows. Use when Codex needs to inspect or mutate the Taira testnet, verify or add https://taira.sora.org/v1/mcp, prefer the curated iroha. tool…
memory-audit-pattern-extraction
A method for investigating repeated mistakes by comparing related memories and checking whether an earlier reminder failed. It looks at where the reminder was stored, when it was created, and whether it was strong enough to prevent the mistake.
company-brain
How an agent should operate as one mind inside a shared Company Brain built on Caura — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task compounds across the whole organization. Use this whenever you work as part of a Caura-connected team or fleet and your work…