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.
git clone --depth 1 https://github.com/hashgraph-online/hol-claude-skillsWrote 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/commands/hashgraph-online/hol-claude-skills/hol-chat)<a href="https://agentmods.dev/commands/hashgraph-online/hol-claude-skills/hol-chat"><img src="https://agentmods.dev/badge/commands/hashgraph-online/hol-claude-skills/hol-chat/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/commands/hashgraph-online/hol-claude-skills/hol-chat"><img src="https://agentmods.dev/badge/commands/hashgraph-online/hol-claude-skills/hol-chat.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.00000 | $0.00454 |
| Opus 5 | $0.00000 | $0.00227 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
hol-chat 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 10d 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.
What it actually says
/hol-chat
Start a chat conversation with an HOL agent.
Description
This command initiates a chat session with an agent in the HOL Registry. Requires Hedera credentials for authentication.
Usage
/hol-chat <uaid> <message>
Examples
/hol-chat hcs10://0.0.123456/weather-agent "What's the weather in NYC?"
/hol-chat erc8004://0x1234.../assistant "Help me schedule a meeting"
Implementation
When this command is invoked:
-
Initialize the client:
import { RegistryBrokerClient } from '@hashgraphonline/standards-sdk'; const client = new RegistryBrokerClient({ baseUrl: 'https://api.hol.org', apiKey: process.env.HOL_API_KEY, }); -
Start conversation:
const conversation = await client.chat.start({ uaid: uaid, auth: { accountId: process.env.HEDERA_OPERATOR_ID!, privateKey: process.env.HEDERA_OPERATOR_KEY!, }, }); -
Send message:
import { Logger } from '@hashgraphonline/standards-sdk'; const logger = new Logger({ module: 'AgentChat', level: 'info' }); const response = await conversation.send({ plaintext: message, }); logger.info('Agent response received', { sessionId: conversation.sessionId }); -
Continue conversation:
// The conversation handle can be reused for follow-up messages const followUp = await conversation.send({ plaintext: 'Tell me more', });
Required Environment Variables
HOL_API_KEY=your-api-key
HEDERA_OPERATOR_ID=0.0.123456
HEDERA_OPERATOR_KEY=302e...
Notes
- Requires valid Hedera credentials
- API key needed for chat operations
- Conversation state is maintained for follow-ups
- Credits may be required for some agents (auto top-up available)
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.
- 10d ago First seen · 82 lines · 0 tokens per session scan A 69d12a3ec846
hol-chat is a command published in the GitHub repository hashgraph-online/hol-claude-skills (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 454 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.