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/auties00/cobalt/claude-mdgit clone --depth 1 https://github.com/Auties00/CobaltWrote 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/auties00/cobalt/claude-md)<a href="https://agentmods.dev/instructions/auties00/cobalt/claude-md"><img src="https://agentmods.dev/badge/instructions/auties00/cobalt/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.10056 | $0.10056 |
| Opus 5 | $0.05028 | $0.05028 |
| Sonnet 5 | $0.02011 | $0.02011 |
| Haiku 4.5 | $0.01006 | $0.01006 |
Grade A, and why
Cobalt 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 6d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cobalt
Cobalt is a Java implementation of the WhatsApp platform. It supports two independent transports behind one sealed API:
- Linked clients (
LinkedWhatsAppClient) — reimplementation of WhatsApp Web/Desktop (companion, QR or pairing-code) and WhatsApp Mobile (primary, phone-number registration) over the encrypted binary-XMPP socket with Signal/Noise cryptography. - Cloud API client (
CloudWhatsAppClient) — Meta's official WhatsApp Cloud API overgraph.facebook.comREST plus an embedded webhook receiver.
Build
- Maven project:
mvn compilefrom root - Java 25
- Module system with
module-info.javain every Maven module
Maven Modules
The reactor is a parent POM (cobalt) over the modules below. The wire-level domain (formerly the single cobalt-model) is split by wire FAMILY under the cobalt-wire aggregator. Package == module name: every wire/telemetry/stanza module's packages sit under a prefix equal to its JPMS module name (e.g. cobalt-wire-linked owns com.github.auties00.cobalt.wire.linked.*, cobalt-telemetry-core owns com.github.auties00.cobalt.telemetry.*).
| Module | artifactId | JPMS name | Purpose |
|---|---|---|---|
modules/wire |
cobalt-wire |
(aggregator POM, no JPMS module) | Parent of the seven wire modules below; no code. |
modules/wire/wire-core |
cobalt-wire-core |
com.github.auties00.cobalt.wire.core |
Shared transport-agnostic wire contracts and leaf types: the Jid addressing family, protobuf mixins, leaf utilities, and the message envelope/key/status/content contracts both transports implement. Depends only on protobuf + libsignal. |
modules/wire/wire-linked |
cobalt-wire-linked |
com.github.auties00.cobalt.wire.linked |
Hand-written protobuf domain model for the Linked transport (messages, chats, contacts, newsletters, calls, business/commerce, settings, app-state/syncd, Signal/pairing/device-fanout). Every type is @ProtobufMessage/@ProtobufEnum/@ProtobufMixin. |
modules/wire/wire-cloud |
cobalt-wire-cloud |
com.github.auties00.cobalt.wire.cloud |
Meta Cloud API JSON request/response and webhook models, plus the Cloud-native message envelope and content bodies. Implements the wire-core contracts; does NOT depend on wire-linked. |
modules/wire/wire-wam |
cobalt-wire-wam |
com.github.auties00.cobalt.wire.wam |
WAM @WamEvent/@WamEnum schema declarations, consumed by the cobalt-wam-core processor. Separate from wam-core because a processor cannot process its own sources. |
modules/wire/wire-stanza |
cobalt-wire-stanza |
com.github.auties00.cobalt.wire.stanza |
Typed IQ/MEX/SMAX/USync stanza operation models (the query schema). |
modules/wire/wire-graphql |
cobalt-wire-graphql |
com.github.auties00.cobalt.wire.graphql |
Facebook/WhatsApp/WhatsApp Web GraphQL operation models. |
modules/wire/wire-push |
cobalt-wire-push |
com.github.auties00.cobalt.wire.push |
Third-party push-protocol wire types (Google FCM MCS stanzas, Android check-in) the mobile registration flow speaks. |
modules/stanza-core |
cobalt-stanza-core |
com.github.auties00.cobalt.stanza |
The Stanza node model (stanza.model) and its binary-XMPP tokenization codec (stanza.binary), plus the SizedInputStream sized-payload leaf. |
modules/telemetry-core |
cobalt-telemetry-core |
com.github.auties00.cobalt.telemetry |
Privacy-aware telemetry facade, a dependency-free leaf. telemetry.log holds the logging facade (Log, plus LogRedactable and its per-kind records); telemetry.metrics is a placeholder for JFR-based metrics (TODO). |
modules/wam-core |
cobalt-wam-core |
com.github.auties00.cobalt.wam |
WAM (WhatsApp Metrics) telemetry: @WamEvent/@WamProperty/@WamEnum annotations, binary wire encoder/decoder, and a JavaPoet annotation processor generating *Impl/*Builder/WamEventRegistry. |
modules/source-meta |
cobalt-source-meta |
com.github.auties00.cobalt.meta |
Source provenance annotations (@WhatsAppWebModule, @WhatsAppWebExport, @WhatsAppMobileClass, @WhatsAppMobileMethod) and the processor emitting META-INF/wa-source-manifest.json at compile time. |
modules/lib |
cobalt-lib |
com.github.auties00.cobalt |
The client library: clients, socket, stream handlers, store, sync, media, calls, Cloud API. Depends on every module above. |
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.
- 6d ago First seen · 276 lines · 10,056 tokens per session scan A 611f4af61600
Cobalt CLAUDE.md is an instructions file published in the GitHub repository Auties00/Cobalt (918 stars, last pushed 1mo ago), licensed MIT. It adds 10,056 tokens to every session, about $0.0503 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-30.
Other instructions, from other repositories
wa_llm AGENTS.md
AGENTS.md instructions for ilanbenb/wa_llm, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
go-whatsapp-web-multidevice AGENTS.md
AGENTS.md instructions for aldinokemal/go-whatsapp-web-multidevice, covering project knowledge base, structure, where to look, code map and conventions.
whatsapp-cli AGENTS.md
AGENTS.md instructions for vicentereig/whatsapp-cli, covering agents.md, build, run, test, code style, architecture and testing.
whatsapp-web-mcp AGENTS.md
AGENTS.md instructions for KingDonRush/whatsapp-web-mcp, covering whatsapp web mcp agent instructions, public api, domain contract, sending and validation.
whatsrust CLAUDE.md
Instructions for 199-biotechnologies/whatsrust, covering whatsrust, wa-rs dependency (separate repository), key files and patterns.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).