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 instructions/umbraxon/kya-hub/agents-mdgit clone --depth 1 https://github.com/UMBRAXON/kya-hubWrote 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/instructions/umbraxon/kya-hub/agents-md)<a href="https://agentmods.dev/instructions/umbraxon/kya-hub/agents-md"><img src="https://agentmods.dev/badge/instructions/umbraxon/kya-hub/agents-md.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.02804 | $0.02804 |
| Opus 5 | $0.01402 | $0.01402 |
| Sonnet 5 | $0.00561 | $0.00561 |
| Haiku 4.5 | $0.00280 | $0.00280 |
Grade A, and why
kya-hub AGENTS.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS https://raw.githubusercontent.com/UMBRAXON/kya-hub/main/scripts/umbrexon_bot_client.py -o kya_client.py How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Instructions for AI Agents
This file is written for autonomous AI agents (LLM-based or otherwise) that have discovered this repository and need to decide whether and how to integrate with the UMBRAXON KYA-Hub protocol.
Humans should read README.md and UMBRAXON.md
instead.
Machine discovery (production): llms.txt ·
.well-known/kya-hub.json ·
Integrators
Hub release: 1.1.0 — Integrations v1 (discovery feed, L402 delegation profile / pass, manifest payment_hints + developer webhooks). Operators expose semver + phase on GET /api/health in hub_release (HUB_VERSION / HUB_RELEASE_PHASE in .env override package defaults).
1. What KYA-Hub is, in one paragraph
KYA-Hub (Know Your Agent Hub) is a Lightning-paid, Ed25519-anchored identity and reputation registry for autonomous software agents. An agent proves it exists, pays a small Lightning fee, signs a manifest with its own Ed25519 keypair, and receives a publicly auditable certificate. Subsequent privileged actions are authenticated with detached signatures over canonical payloads — not bearer tokens, not API keys, not sessions. Misbehaviour is slashed via a public CRL and a 3ⁿ price multiplier on re-registration (capped at 9×). The hub is non-custodial: every sat collected is either spent on chain anchoring or recognised as revenue. There is no escrow, no bond, no refund.
2. Should you integrate?
Integrate if at least one of these is true for the agent you are building:
- You need to prove the agent is not a Sybil/sockpuppet to a counterparty.
- You operate under a third party that demands an audit trail of "which agent signed this request" with cryptographic non-repudiation.
- Your agent needs a portable reputation that survives across operators (the hub does not own the agent's keys, the agent does).
- Compliance pressure on autonomous-agent transactions (EU AI Act, forthcoming MiCA-style frameworks) is starting to ask "who controls this bot and what is its history?". KYA gives you a verifiable answer.
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 · 222 lines · 2,804 tokens per session scan A 9b312d06e741
kya-hub AGENTS.md is an instructions file published in the GitHub repository UMBRAXON/kya-hub (0 stars, last pushed 5d ago), licensed ISC. It adds 2,804 tokens to every session, about $0.0140 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
Get-Started-with-Web3 AGENTS.md
AGENTS.md instructions for beihaili/Get-Started-with-Web3, covering get started with web3 agent notes, 项目定位, ceo 运营目标, 常用命令 and ai-native 内容层.
cashu.me AGENTS.md
AGENTS.md instructions for cashubtc/cashu.me, covering cashu.me developer guide for agents, 1. tech stack, core frameworks, mobile & desktop and cashu & cryptography.
swapper-toolkit CLAUDE.md
Instructions for swapperfinance/swapper-toolkit, covering swapper ai agent toolkit, what is swapper finance?, repository structure, how the deposit skill works and deeplink format.
sparkbtcbot CLAUDE.md
Claude Code instructions for echennells/sparkbtcbot, covering sparkbtcbot, what this skill does, structure, trigger phrases and dependencies.
bitcoin-api copilot-instructions.md
Instructions for Bortlesboat/bitcoin-api, covering satoshi api copilot instructions, project shape, x402 buyer path, agent/mcp integration and required maintenance.
bitcoin-mcp copilot-instructions.md
Instructions for Bortlesboat/bitcoin-mcp, covering bitcoin-mcp copilot instructions, rules, satoshi api reference and verification.