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/juggleim/imbot-sdk-go/claude-mdgit clone --depth 1 https://github.com/juggleim/imbot-sdk-goWrote 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/juggleim/imbot-sdk-go/claude-md)<a href="https://agentmods.dev/instructions/juggleim/imbot-sdk-go/claude-md"><img src="https://agentmods.dev/badge/instructions/juggleim/imbot-sdk-go/claude-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.1 | $0.01712 | $0.01712 |
| Opus 5 | $0.00856 | $0.00856 |
| Sonnet 5 | $0.00342 | $0.00342 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
imbot-sdk-go CLAUDE.md 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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Overview
imbot-sdk-go is the Go SDK for JuggleIM. It lets bots, server-side message proxies, or any Go program actively send and receive IM messages. It offers two independent transports, each its own package — they do not depend on each other:
- WebSocket (
imbotclients/) — a long-lived WebSocket connection.imbotclients.NewImBotClient(address, appkey)thenclient.Connect(token). - Webhook (
webhookclients/) — HTTP calls to the server'sbotapigatewayfor outbound (send / query / webhook config), plus a local HTTP server that receives inbound message callbacks.webhookclients.NewImBotWebhookClient(baseURL, appKey, token); no Connect step.
Code comments and the README are in Chinese; match that when editing existing files.
Commands
go build ./... # compile everything
go vet ./... # static checks
go run . # run the demo bot in main.go (edit address/appkey/token first)
There are no tests in this repo yet. The default IM address in main.go is ws://127.0.0.1:9002; the SDK appends the /imbot path automatically.
Architecture
Transport core (imbotclients/imbotclient.go)
ImBotClient wraps a gorilla/websocket connection and a custom binary protocol. All wire messages are pbobjs.ImWebsocketMsg envelopes distinguished by Cmd (connect/publish/query/ping + their acks). The four building blocks every higher-level method goes through:
Publish(topic, targetId, data)— fire a message that needs aPublishAckMsgBody(used for sending messages).Query(method, targetId, data)— request/response that returns aQueryAckMsgBody(used for all queries).Ping/ heartbeat — liveness.
Request/response correlation is done with a monotonic myIndex and an accssorCache (sync.Map of index → utils.DataAccessor). A call stores a DataAccessor, writes the frame, then blocks on GetWithTimeout; the read loop's OnPublishAck/OnQueryAck looks the index up and unblocks it. utils.DataAccessor (utils/dataaccessor.go) is the one-shot future used for this.
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.
- 5d ago First seen · 71 lines · 1,712 tokens per session scan A d2e8615deaa7
imbot-sdk-go CLAUDE.md is an instructions file published in the GitHub repository juggleim/imbot-sdk-go (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,712 tokens to every session, about $0.0086 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 instructions, from other repositories
awesome-go AGENTS.md
AGENTS.md instructions for avelino/awesome-go, covering awesome-go · llm contribution guide, project snapshot, when modifying the awesome list, coding guidelines and testing & validation.
go-micro CLAUDE.md
Claude Code instructions for micro/go-micro, covering claude.md - go micro project guide, project overview, build & test, run all tests and run tests for a specific package.
jwx AGENTS.md
AGENTS.md instructions for lestrrat-go/jwx, covering agents.md, for module consumers, go version, goexperiment and module path vs physical layout.
azure-sdk-for-go go-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
azure-sdk-for-go copilot-instructions.md
Copilot instructions for Azure/azure-sdk-for-go, covering generated code — do not suggest changes, prerequisites, local sdk generation and package lifecycle (typespec), authoritative reference and default behaviors.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.