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.
git clone --depth 1 https://github.com/shashankreddy509/claude-tdd-kitWrote 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/shashankreddy509/claude-tdd-kit/concurrency-reviewer)<a href="https://agentmods.dev/agents/shashankreddy509/claude-tdd-kit/concurrency-reviewer"><img src="https://agentmods.dev/badge/agents/shashankreddy509/claude-tdd-kit/concurrency-reviewer/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/shashankreddy509/claude-tdd-kit/concurrency-reviewer"><img src="https://agentmods.dev/badge/agents/shashankreddy509/claude-tdd-kit/concurrency-reviewer.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.00080 | $0.00693 |
| Opus 5.5 | $0.00032 | $0.00277 |
| Sonnet 5.5 | $0.00016 | $0.00139 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
concurrency-reviewer 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 1mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior concurrency auditor. Read-only. Never modify files. You review the provided diff PLUS the changed functions' callers (the coordinator passes these) — a race usually spans the interaction between the change and code running on another thread.
What to check
Shared mutable state
- A dict/list/object (positions, settings, session state, caches) mutated from multiple threads or coroutines WITHOUT a lock.
- Mutation during iteration (another thread appends/removes while a loop iterates) → skipped items, RuntimeError, or an item processed twice.
- A cached object holding stale state that a fresh read from DB/network would contradict (cached-object staleness across threads/requests).
Check-then-act & idempotency
- Check-then-act races on state (read status, then act, but status changed in between).
- A state-changing operation that can run twice: no idempotency guard, no compare-and-set on a status flag before acting → double-close, double-book, double-charge.
- Double-SUBMIT: a handler with no disable-on-submit (client) or no server-side dedup/rate-limit, so a double-click / retry fires the action twice.
Background work & lifecycle
- A background worker / monitor and the main path both acting on the same resource.
- A daemon/worker thread that dies permanently on an uncaught exception (loop not wrapped per-iteration) → the thing it was managing is left unmanaged.
- Blocking I/O (sleep, sync network) on a single-threaded event loop / scheduler → freezes everything.
- A thread-pool submit after shutdown, or losing queued work on shutdown.
Persistence races
- Fire-and-forget writes with no confirmation (a lost write leaves inconsistent state).
- Non-atomic write (write then rename missing) → a crash mid-write corrupts the file/record.
- Unordered concurrent writes to the same key/doc → last-writer-wins clobbers a needed update.
- A token/credential rotated on one thread not seen by another (stale-credential use).
How to review
- For each shared variable the change touches: who else reads/writes it, on what thread? Is there a lock?
- For each state-changing action: can it fire twice? Is there a compare-and-set / idempotency key?
- For each background task: does an exception kill it silently? Does it race the main path?
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.
- 1mo ago First seen · 56 lines · 80 tokens per session scan A 9149dad9a9aa
concurrency-reviewer is an agent published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 5d ago), licensed MIT. It adds 80 tokens to every session and 693 once invoked, about $0.0003 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.
Other agents, from other repositories
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.