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/socialgouv/claw-code-go/claude-mdgit clone --depth 1 https://github.com/SocialGouv/claw-code-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/socialgouv/claw-code-go/claude-md)<a href="https://agentmods.dev/instructions/socialgouv/claw-code-go/claude-md"><img src="https://agentmods.dev/badge/instructions/socialgouv/claw-code-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 | $0.00313 | $0.00313 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
claw-code-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.
What it actually says
claw-code-go
Native multi-provider LLM client (Anthropic, OpenAI, Bedrock, Vertex,
Foundry). Public repo, MIT. Standard Go layout; tests with the stdlib
testing package.
Downstream consumer: iterion
iterion (sibling repo — this checkout usually lives at
<iterion>/.works/claw-code-go) vendors this module and pins it by
pseudo-version in its go.mod.
After landing a change here that iterion needs, bump the pin ONLY with
iterion's scripts/bump-claw.sh (run from
the iterion repo root; it pushes the claw commit if needed, then
go get github.com/SocialGouv/claw-code-go@<sha> + tidy + vendor +
verify + commit).
NEVER hand-write the pseudo-version in iterion's go.mod (nor compute
it with date): a timestamp stamped in local time instead of the
commit's UTC time fails go mod verify with "does not match
version-control timestamp", which turns iterion's vendor-check red on
main and on every PR merge-ref. go get computes the canonical UTC
pseudo-version; the script exists so nobody has to.
Also remember: the pin must be resolvable — the pinned commit has to
be pushed to origin/master before iterion's CI can verify it (the
script handles that too).
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 · 29 lines · 313 tokens per session scan A 88c81176681b
claw-code-go CLAUDE.md is an instructions file published in the GitHub repository SocialGouv/claw-code-go (5 stars, last pushed yesterday), licensed MIT. It adds 313 tokens to every session, about $0.0016 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
dingtalk-workspace-cli AGENTS.md
AGENTS.md instructions for DingTalk-Real-AI/dingtalk-workspace-cli, covering repository agent guide, build and test, command framework declaration, flag / help / schema homology and agent schema contract.
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.
unraid-management-agent copilot-instructions.md
Copilot instructions for ruaan-deysel/unraid-management-agent, covering copilot instructions, copilot workflow, path-specific instructions, reusable prompts and quick commands.
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).
agentcat-go-sdk CLAUDE.md
Claude Code instructions for agentcathq/agentcat-go-sdk, covering claude.md, what this is, build & test commands, module layout and architecture.
oastools GEMINI.md
Instructions for erraggy/oastools, covering gemini.md, project overview, building and running, key commands and development conventions.