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 xonovex/platform --skill lock-free-guidegit clone --depth 1 https://github.com/xonovex/platformWrote 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/xonovex/platform/lock-free-guide)<a href="https://agentmods.dev/skills/xonovex/platform/lock-free-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/lock-free-guide/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/skills/xonovex/platform/lock-free-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/lock-free-guide.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.00103 | $0.01436 |
| Opus 5.5 | $0.00041 | $0.00574 |
| Sonnet 5.5 | $0.00021 | $0.00287 |
| Haiku 4.5 | $0.00010 | $0.00144 |
Grade A, and why
lock-free-guide 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lock-Free / Wait-Free Concurrency Guidelines
Choose concurrency primitives by their progress guarantees, memory ordering, and reclamation requirements; verify them under contention.
Requirements
- C11 atomics (
<stdatomic.h>); applies to systems code with atomic, threading, and job-scheduling primitives.
Essentials
- No data races - Every shared mutable location touched by 2+ threads is atomic or lock-protected, see references/memory-model.md
- CAS loops retry -
compare_exchange_weakin a loop; reload the expected value on failure, see references/atomics-and-cas.md - Lock-free needs reclamation - Removing a node from a shared structure is not freeing it, see references/safe-memory-reclamation.md
- Measure, do not assume - Locks are often faster; profile before going lock-free, see references/progress-guarantees.md
Memory model
- Progress guarantees - wait-free ⊃ lock-free ⊃ obstruction-free ⊃ blocking, see references/progress-guarantees.md
- Happens-before - Acquire/release builds the ordering that makes writes visible, see references/memory-model.md
- Orderings - relaxed/acquire/release/acq_rel/seq_cst + fences, see references/memory-ordering.md
Building blocks
- Atomics & CAS - load/store/exchange/fetch_*/compare_exchange, weak vs strong, see references/atomics-and-cas.md
- ABA problem - CAS can't see a value changed away and back; tag pointers or reclaim safely, see references/aba-problem.md
- False sharing - Pad/align hot per-thread and atomic fields to their own cache line, see references/false-sharing.md
Data structures
- SPSC ring - One producer, one consumer, no CAS, see references/spsc-ring-buffer.md
- MPSC queue - Intrusive: producers XCHG tail, consumer walks next, see references/mpsc-queue.md
- MPMC bounded - Per-cell sequence numbers, ABA-free, see references/mpmc-bounded-queue.md
- Lock-free stack - CAS on head; needs reclamation for pop, see references/lock-free-stack.md
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- eval-queries.json 4.7 KB
- evals.json 3.2 KB
- moon.yml 166 B
- references/aba-problem.md 2.7 KB
- references/atomics-and-cas.md 3.3 KB
- references/false-sharing.md 1.9 KB
- references/lock-free-stack.md 2.9 KB
- references/locks-and-backoff.md 4.1 KB
- references/memory-model.md 2.8 KB
- references/memory-ordering.md 2.0 KB
- references/mpmc-bounded-queue.md 5.3 KB
- references/mpsc-queue.md 3.6 KB
- references/progress-guarantees.md 2.6 KB
- references/safe-memory-reclamation.md 4.5 KB
- references/scalable-architecture.md 4.1 KB
- references/spsc-ring-buffer.md 2.6 KB
- references/testing-and-verification.md 3.4 KB
- SOURCES.md 3.7 KB
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 Changed · +2 lines 78e9542ef18d
- 1mo ago First seen · 68 lines · 103 tokens per session scan A c625e62c4f8f
lock-free-guide is a skill published in the GitHub repository xonovex/platform (6 stars, last pushed 5d ago), licensed MIT. It adds 103 tokens to every session and 1,436 once invoked, about $0.0004 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-09-08.
Other skills, from other repositories
kastell-research
Read-only Kastell codebase exploration. Use when tracing a bug across files, mapping callsites before refactoring, or exploring unfamiliar subsystems. Runs in isolated context with Explore agent.
System Healthcheck
Run a lightweight, non-destructive system healthcheck — disk usage, memory, CPU load, process count, hostname — and store a structured snapshot in session memory. Use when the user says "run a healthcheck", "check system health", "how's the server doing", "is everything ok", or asks for a status/diagnostics snapshot…
docker-management
Docker container lifecycle management, Dockerfile authoring, and debugging.
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.