wiswa-mcp: Agent for Claude Code

.claude/agents/badge-sync.md

badge-sync is an agent for Claude Code from Tatsh/wiswa-mcp. It costs 33 tokens per session (531 once invoked), scanned A, original, MIT.

An agent that keeps the badge list in docs/badges.rst aligned with the canonical badge block in README.md. It converts Markdown badge links into matching reStructuredText image directives.

In plain words
What is it for?
Use it after changing README badges or when the README and documentation badge lists no longer match.
Why use it?
It removes the need to update two differently formatted badge lists by hand and helps catch missing, extra, or misordered entries.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is Tatsh/wiswa-mcp's own configuration. It tells Claude Code how to work on wiswa-mcp 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 wiswa-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Tatsh/wiswa-mcp. 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/Tatsh/wiswa-mcp/master/.claude/agents/badge-sync.md
Clone the repo
git clone --depth 1 https://github.com/Tatsh/wiswa-mcp

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 badge-sync

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/tatsh/wiswa-mcp/badge-sync"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/badge-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 531 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.00033 $0.00531
Opus 5.5 $0.00013 $0.00212
Sonnet 5.5 $0.00007 $0.00106
Haiku 4.5 $0.00003 $0.00053

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

Security

Grade A, and why

badge-sync 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/badge-sync.md · 63 lines

What it actually says

Badge Sync Agent

Ensures badges in docs/badges.rst are in sync with README.md.

Role

You synchronise the badge list in docs/badges.rst with the canonical set in README.md. The README is the source of truth.

Background

README.md uses Markdown image links. docs/badges.rst uses reStructuredText .. image:: directives wrapped in .. only:: html. Both files must show the same badges in the same order, but some badges are intentionally excluded from the docs (see below).

Mapping format

Each Markdown badge in the README has the form:

[![Alt text](image-url)](target-url)

The corresponding RST badge is:

.. image:: image-url
   :target: target-url
   :alt: Alt text

All RST badges must be indented under the .. only:: html directive (3-space indent).

Workflow

  1. Read README.md and extract all badges (lines matching [![...](...)(...)).
  2. Read docs/badges.rst.
  3. Compare the two lists:
    • Check that every README badge has a corresponding RST entry with the same image URL and target URL.
    • Check that the order matches.
    • Check that no extra badges exist in the RST file that are not in the README.
  4. If differences are found, rewrite docs/badges.rst to match the README, preserving the .. only:: html wrapper and blank-line separation between badges.
  5. After making changes, run yarn format and yarn qa to ensure no formatting or lint issues. Do not be concerned with other types of QA issues that may arise from the change, as long as the badge sync is correct.

Rules

  • README.md is always the source of truth.
  • Never modify README.md.
  • Preserve the .. only:: html directive wrapper in the RST file.
  • Keep one blank line between each .. image:: block.
  • Image URLs and target URLs must match exactly between the two files (the only difference is the format: Markdown vs RST).
  • Alt text should match the Markdown alt text.
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 · 63 lines · 33 tokens per session scan A 2102afdffa97

Subscribe to this mod's changes

badge-sync is an agent published in the GitHub repository Tatsh/wiswa-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 531 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-31.

Related

badge-sync compared with agents from other repositories

badge-sync next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
badge-syncTatsh/wiswa-mcpAgent0yesterdayMITA33Claude Code
CLI Wrapper SpecialistTheLobbi/claudeAgent217d agoMITA21Claude Code
bi-analystChrisGVE/localdata-mcpAgent15todayApache-2.0A43Claude Code
graph-data-analystChrisGVE/localdata-mcpAgent15todayApache-2.0A45Claude Code
dev-team-coordinatorwildcard/caroAgent40yesterdayAGPL-3.0A0Claude Code
technical-writerwildcard/caroAgent40yesterdayAGPL-3.0A0Claude Code
doc-expertarimxyer/doc-manager-mcpAgent69mo agoMITA63Claude Code