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.
curl -O https://raw.githubusercontent.com/Tatsh/wiswa-mcp/master/.claude/agents/badge-sync.mdgit clone --depth 1 https://github.com/Tatsh/wiswa-mcpWrote 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/agents/tatsh/wiswa-mcp/badge-sync)<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.
<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>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.00033 | $0.00531 |
| Opus 5 | $0.00016 | $0.00266 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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 8d 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
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:
[](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
- Read
README.mdand extract all badges (lines matching[(...)). - Read
docs/badges.rst. - 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.
- If differences are found, rewrite
docs/badges.rstto match the README, preserving the.. only:: htmlwrapper and blank-line separation between badges. - After making changes, run
yarn formatandyarn qato 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.mdis always the source of truth.- Never modify
README.md. - Preserve the
.. only:: htmldirective 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.
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.
- 8d ago First seen · 63 lines · 33 tokens per session scan A 2102afdffa97
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.0002 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 agents, from other repositories
CLI Wrapper Specialist
Expert in creating command-line interfaces for LangGraph agents, with streaming output and interactive capabilities.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
operations-analyst
Operations and process analysis agent. Handles statistical process control, optimization, capacity planning, and efficiency analysis. Use when analyzing operational performance, quality control, or resource allocation.
claude-design-frontend-engineer
Use this agent when the work touches Caro's brand identity — UI/UX audits, screenshot triage, communication with the claude.ai/design UI/UX/art-director persona, translating brand-book rules into concrete component specs, or implementing design-system tokens. Critically, ALWAYS spawn this agent for tasks that involve…
bi-analyst
Business intelligence agent. Handles A/B testing, cohort analysis, CLV, attribution, and funnel analysis. Translates statistical results into business recommendations. Use for business metric analysis and experiment evaluation.
graph-data-analyst
Graph data and network analysis agent. Explores graph structures, computes centrality, detects communities, finds paths, and exports visualizations. Use when working with network, dependency, or relationship data.