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 skills/new1direction/korgex/concurrency-correctnessnpx skills add New1Direction/korgex --skill concurrency-correctnessgit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/skills/new1direction/korgex/concurrency-correctness)<a href="https://agentmods.dev/skills/new1direction/korgex/concurrency-correctness"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/concurrency-correctness.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.00019 | $0.00344 |
| Opus 5 | $0.00010 | $0.00172 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
concurrency-correctness 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.
What it actually says
Concurrency bugs are nondeterministic and brutal to debug — get the design right up front rather than patching symptoms.
- Find the shared mutable state. Races happen only where two flows touch the same mutable data. Enumerate it. The safest design shares nothing — pass messages / immutable data instead.
- Protect every access, consistently. If state is shared, guard ALL reads and writes with the same lock (or use an atomic/concurrent structure). A single unguarded access defeats the lock.
- Avoid deadlock. Acquire multiple locks in a consistent global order; hold them as briefly as possible; don't call out to unknown code while holding one.
- Don't assume ordering or atomicity. "It worked when I ran it" proves nothing
— interleavings you didn't see still happen.
check-then-actis a race unless atomic. - Wait on conditions, not sleeps (see condition-based-waiting). For tests of
concurrent code, synchronize on events/barriers — never
sleepto dodge a race. - Bound and clean up. Cap parallelism; ensure every spawned task is awaited or cancelled; propagate errors from workers instead of losing them.
Red flags: a sleep "fixing" flakiness, a lock around some-but-not-all accesses,
shared mutable state with no guard, swallowed worker exceptions.
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 · 29 lines · 19 tokens per session scan A bc69f55af13f
concurrency-correctness is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 344 once invoked, about $0.0001 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 skills, from other repositories
vibe-ui-design
Use when designing UI/UX, defining design systems, choosing color palettes, typography, spacing, or component primitives. Triggers on "design system", "design tokens", "color palette", "UI 设计", "深色工业风", "design language".
vibe-ui-beautify
Use when adding animations, micro-interactions, 3D effects, glassmorphism, or "juicy" tactile feedback to UI components. Triggers on "animation", "hover effect", "transition", "动效", "果汁感", "Framer Motion", "GSAP", "3D 视效".
vibe-security
Use when performing security audits, vulnerability scanning, dependency checks, or secure code reviews. Triggers on "security audit", "scan vulnerabilities", "安全审查", "漏洞扫描", "OWASP", "dependency check".
vibe-autopilot
Use this skill when the user requests fully autonomous, 24/7 hands-free development without human intervention.
vibe-test
Use when writing tests, performing unit testing, integration testing, or verifying system functionality. Triggers on "write tests", "run tests", "add unit test", "TDD", "测试", "跑测试".
vibe-assets
Use when the project needs real images, icons, fonts, illustrations, or logos. Automatically fetches and integrates assets from CDN libraries and AI generation APIs. Triggers on "images", "icons", "fonts", "assets", "素材", "图片资源", "图标库", "字体".