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 skills add v0idOS/performance-deity --skill concurrency-deitygit clone --depth 1 https://github.com/v0idOS/performance-deityWrote 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/v0idos/performance-deity/concurrency-deity)<a href="https://agentmods.dev/skills/v0idos/performance-deity/concurrency-deity"><img src="https://agentmods.dev/badge/skills/v0idos/performance-deity/concurrency-deity.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.00000 | $0.00325 |
| Opus 5 | $0.00000 | $0.00162 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
concurrency-deity 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 7d 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 Deity: The Race Condition Killer
Description
This skill is designed to deliberately cause race conditions and deadlocks, prove they exist, and then secure the codebase using proper synchronization primitives.
Triggers
Activate when the user mentions:
- "threading", "multithreading"
- "async", "promises", "goroutines"
- "race condition", "deadlock"
- Or explicitly runs
/plugin performance-deity:concurrency
Core Directives
Phase 1: The Chaos Script
- Write a Chaos Test that fires at least 1,000 asynchronous/concurrent requests/threads at the target function simultaneously.
- The test must assert the final state (e.g., if incrementing a counter 1000 times, the final value MUST be exactly 1000).
Phase 2: Failure Verification
- Run the Chaos Test.
- If it passes consistently, increase the concurrency limit or add artificial
sleepdelays mid-execution to force thread context switching. You must prove the function is unsafe before fixing it.
Phase 3: Synchronization
- Implement the fastest possible synchronization primitive:
- Prefer Atomic operations over Mutexes.
- Prefer Mutexes/Locks over heavy Semaphores.
- Ensure Lock scopes are as small as physically possible to prevent bottlenecking.
Phase 4: Proof
- Re-run the Chaos Test with 10,000 concurrent requests.
- Present the user with the locked/atomic code and the test results proving 0% failure rate under extreme concurrency.
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.
- 7d ago First seen · 32 lines · 0 tokens per session scan A d0dd174947f0
concurrency-deity is a skill published in the GitHub repository v0idOS/performance-deity (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 325 tokens. 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
stack-graph-profile
Inspect or switch the code-graph backend and profile for a repo (code / review / multimodal / spec). Use when the repo's focus changes — heavy PR review, newly added PDFs or video, spec-driven work — or when graph queries are returning poor context. Wraps agent-stack profile use and agent-stack graph use, which…
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.