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 baphuongna/pi-crew --skill state-mutation-lockinggit clone --depth 1 https://github.com/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/state-mutation-locking)<a href="https://agentmods.dev/skills/baphuongna/pi-crew/state-mutation-locking"><img src="https://agentmods.dev/badge/skills/baphuongna/pi-crew/state-mutation-locking.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.00014 | $0.00591 |
| Opus 5 | $0.00007 | $0.00296 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
state-mutation-locking 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
state-mutation-locking
Use this skill before modifying pi-crew run state.
Source patterns distilled
src/state/locks.ts— run-level sync/async lockssrc/state/state-store.ts— manifest/tasks persistencesrc/state/contracts.ts— allowed status transitionssrc/state/mailbox.ts,src/state/task-claims.ts,src/state/atomic-write.tssrc/runtime/crash-recovery.ts,src/runtime/stale-reconciler.ts,src/runtime/team-runner.ts
Rules
- Mutations to a run's
manifest.json,tasks.json, mailbox delivery state, claims, or recovery status must be protected by a run lock when concurrent actions are possible. - Re-read manifest/tasks inside the lock before making a decision; pre-lock reads are only for locating the run.
- Persist with atomic write helpers (
atomicWriteJson, async variants, or state-store helpers). Do not partially write JSON files. - Respect status contracts. Do not transition terminal tasks/runs unless the action explicitly supports force semantics.
- Separate analysis from persistence: pure reconcilers should return intended repaired state; locked callers should persist it.
- In retry/resume paths, reload fresh task status immediately before execution and skip if the task is no longer retryable/runnable.
- Include event-log entries for externally visible state changes.
Enforcement — State Mutation Locking Gate
Before mutating run state, verify:
- Run lock acquired before mutation (concurrent actions possible)
- Manifest/tasks re-read inside the lock before decision
- Atomic write helpers used (atomicWriteJson or state-store helpers)
- Status contracts respected (no terminal transitions without force semantics)
- Event-log entries emitted for externally visible state changes
- Retry paths reload fresh task status before execution
If ANY answer is NO → Stop. Verify locking and atomicity before mutating.
Anti-patterns
- Reading state, waiting/doing async work, then writing the old copy.
- Updating
tasks.jsonfrom a reconciler or watcher without a lock. - Cancelling/responding to runs owned by another session.
- Using
fs.writeFileSyncfor JSON state outside atomic helpers.
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 · 64 lines · 14 tokens per session scan A 7295e3fab077
state-mutation-locking is a skill published in the GitHub repository baphuongna/pi-crew (51 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 591 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-30.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.