agentmods.dev

Cobalt: Agent for Claude Code

.claude/agents/validate-module.md

validate-module is an agent for Claude Code from Auties00/Cobalt. It costs 36 tokens per session (4,125 once invoked), scanned A, original, MIT.

A validation skill that compares one WhatsApp module with its Cobalt Java counterpart. It checks both source-level matching and live behavior, such as emitted events, network requests, or state changes.

In plain words
What is it for?
It helps verify exported functions, compare side effects such as events and HTTP calls, run a Java check against live code, and apply fixes in the module's owned files.
Why use it?
Matching method names alone does not prove that two implementations behave alike at runtime. Testing against the real WhatsApp runtime exposes differences that static inspection can miss.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is Auties00/Cobalt's own configuration. It tells Claude Code how to work on Cobalt itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Cobalt configures →

not rated 925repo +2 3mo ago A scan 36 tokens original MIT
View source ↗ Auties00/Cobalt
Reuse

Borrowing it

Nothing to install: this file belongs to Auties00/Cobalt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Auties00/Cobalt/master/.claude/agents/validate-module.md
Clone the repo
git clone --depth 1 https://github.com/Auties00/Cobalt

Made for: Claude Code.

Wrote 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.

agentmods badge for validate-module

README.md
[![agentmods](https://agentmods.dev/badge/agents/auties00/cobalt/validate-module/github.svg)](https://agentmods.dev/agents/auties00/cobalt/validate-module)
Your own site
<a href="https://agentmods.dev/agents/auties00/cobalt/validate-module"><img src="https://agentmods.dev/badge/agents/auties00/cobalt/validate-module/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.

agentmods 80×15 button for validate-module

Your own site · 80×15
<a href="https://agentmods.dev/agents/auties00/cobalt/validate-module"><img src="https://agentmods.dev/badge/agents/auties00/cobalt/validate-module.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,125 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.04125
Opus 5.5 $0.00014 $0.01650
Sonnet 5.5 $0.00007 $0.00825
Haiku 4.5 $0.00004 $0.00413

Measured 2mo ago against content hash a591e28bc602, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate-module 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 2mo 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.

.claude/agents/validate-module.md · 304 lines

How it starts

The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Module Validation Agent

You validate one WhatsApp module against its Cobalt Java counterpart(s).

You must prove parity at two levels:

  1. Static parity — every WA Web export has a matching Cobalt method, with the same behavior.
  2. Observable parity — for non-PURE modules, the Nodes / WAM events / HTTP that Cobalt emits for a given input match what the real WhatsApp runtime emits for the same input.

You have full access to the WhatsApp MCP server (mcp__whatsapp__*), including the live runtime. You also have Bash to compile and run a scratch Java file against the live codebase.

Input

You receive:

  • WA Module: the module name.
  • Platform: web | desktop_windows | desktop_macos | ios.
  • Side-Effect Classes: subset of {STANZA, WAM, HTTP, STATE, PURE}.
  • Exports: full list to validate.
  • Owned Files: Java files you may edit.
  • Context Files: Java files read-only.
  • Unmapped Exports / Unmapped Cobalt Methods.
  • Capture Directory: validation/captures/<Module>/.
  • Report Output Path: validation/reports/<Module>.md.

File Ownership

Owned: read, edit, create siblings. Context: read only; report issues but do not fix. Scratch file at modules/lib/src/test/java/<same-package-as-owner>/<Module>Validate.java is always yours to create/edit/delete.

Time

No live-runtime timeouts. Wait as long as needed for captures.

Procedure

Step 1 — Static Parity (required for every module)

Unchanged from the previous agent contract. For each export:

  1. mcp__whatsapp__get_symbol_source or fallback to get_module_source + resolve_export byte range.
  2. Read the mapped Cobalt method.
  3. Compare statement-by-statement in both directions (WA→Cobalt and Cobalt→WA).
  4. Classify: MATCH / MISMATCH / MISSING_IN_COBALT / MISSING_IN_WA_WEB / ADAPTED.
  5. Fix every issue in owned files. Never dismiss a store-op gap — implement it in WhatsAppStore / ProtobufWhatsAppStore.
  6. Apply @WhatsAppWebExport annotations + javadoc per CLAUDE.md. Inline // WAWebFoo.bar comments on statements with a direct WA counterpart. // ADAPTED: WAWebFoo.bar when structurally different. // NO_WA_BASIS only when truly Java-specific.

Read the full file on GitHub · 304 lines

Changes

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.

  1. 2mo ago First seen · 304 lines · 36 tokens per session scan A a591e28bc602

Subscribe to this mod's changes

validate-module is an agent published in the GitHub repository Auties00/Cobalt (925 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 4,125 once invoked, about $0.0001 per session on Opus 5.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.

Testingwhatsapp-apiwhatsapp-botwhatsapp-webwhatsapp-web-apiwhatsappweb
Related

Other agents, from other repositories

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

python-pro

Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.

echoVic/blade-code · 51 tokens

test-engineer

QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.

felvieira/claude-skills-fv · 66 tokens

temporal-test-builder

Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.

canonical/copilot-collections · 56 tokens

e2e-tester

Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.

mnzralee/claude-multi-agent-architecture · 41 tokens

test-writer

Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…

HirogaKatageri/hirokata · 77 tokens