More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Git Agent Lock — Part 1: Atomic File Lock & TTL Guard

    1

    Atomic per-file locking and automatic TTL stale reclamation to prevent agent clobbering in multi-agent Git workflows.

    Free

    Security scanned
    Git Agent Lock — Part 1: Atomic File Lock & TTL Guard

    Git Agent Lock — Part 1: Atomic File Lock & TTL Guard

    Example session with this skill installed

    Acquire an atomic lock on 'src/auth/jwt_handler.py' for subagent-auth-worker with a 300s TTL.

    • Read your context and instructions
    • Compiled the git agent lock

    ✅ Lock acquired on 'src/auth/jwt_handler.py' for agent 'subagent-auth-worker' (TTL: 300s)

    ================================================================
    🔒 GIT AGENT LOCK PART 1 — Atomic File Lock & TTL Guard (v1.0.0)

    Active Locks: 1

    🔒 #1 Path: [src/auth/jwt_handler.py]
    Held by: subagent-auth-worker | TTL Remaining: 300s
    Reason: Updating refresh token signature verification

    ================================================================

    Next Steps:

    Target file locked exclusively. Concurrent agents requesting this resource will be blocked until release or TTL expiration.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Git Agent Lock — Part 1: Atomic File Lock & TTL Guard

    Running concurrent AI coding agents or subagents on a shared repository frequently causes race conditions: two agents modifying the same file simultaneously, clobbering edits, and corrupting working copies.

    Git Agent Lock Part 1 is a deterministic, lightweight atomic file locking system built specifically for multi-agent workflows across Claude Code, Cursor, Windsurf, and Google Antigravity.

    ⚡ Key Capabilities:

    • Atomic POSIX File Locks: Agents acquire explicit locks on target files before touching code, preventing race conditions.
    • TTL Stale Lock Reclamation: Dead agent processes never freeze your workflow; expired locks automatically release after a configurable TTL.
    • Agent Ownership Enforcement: Only the agent holding a lock (or an admin override) can release it.
    • Deterministic CLI & JSON Output: Seamlessly integrate lock checks into agent bash steps and subagent coordinators.

    📦 What's Included:

    • scripts/git_agent_lock_core.py — Production locking CLI and Python API
    • scripts/test_git_agent_lock_core.py — Automated unit test suite (100% pass)
    • references/git_agent_lock_core_guide.md — Operator manual & concurrency safety policies
    • Universal SKILL.md — Lean Core architecture (< 40 lines)

    🚀 Upgrade Path to Git Agent Lock Pro Suite:

    Part 1 covers standalone atomic file locks. For pre-commit staging audits, dynamic Git worktrees, deadlock graph detection, and causal forensics integration, check out the Git Agent Lock Pro Suite ($29) on Agensi.

    🔒 100% Local-First & Zero Telemetry

    Runs 100% locally on your machine via standard Git and Python. Zero network calls, zero tracking.

    Requires Python 3. Logic is local to the repository and does not sync locks across remote forks or different machines without a shared file system.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 16 days ago

    • Free with an Agensi account

    Requires

    git
    python3

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Manages local lock files in .agent/git_locks with zero cloud network calls.

    Listed16 days ago

    What's inside

    Frequently Asked Questions

    This skill prevents 'file clobbering' in multi-agent workflows by creating a shared technical barrier that ensures only one AI agent can write to a specific file at any given time. It solves the issue of race conditions where multiple agents might overwrite each other's work or corrupt the Git index.

    The skill is designed for Python 3 environments and works with any AI agent framework that can execute local scripts. It acts as a local resource manager for your Git repository, making it compatible with most autonomous agent swarms.

    The TTL (Time-To-Live) guard is a safety timer that automatically expires a lock if an agent hangs or crashes. This prevents 'deadlocks' where a file remains permanently inaccessible because an agent failed to manually release its lock.

    You will receive the core Python implementation of the atomic locking logic, the status monitoring utility, and the maintenance tools for clearing stale locks. This 'Part 1 Core' package includes everything needed to integrate file-level concurrency control into your local agent workflows.

    No, this version is a local file-locking mechanism optimized for agents working on the same machine or filesystem. It does not provide server-side distributed locking for human team members working from different remote locations.

    Installation is straightforward: ensure you have Python 3 installed, then integrate the lock and release commands into your agent's toolset. Once configured, your agents will call the skill to 'Acquire' a lock before beginning any file edit.

    New in Agents & Orchestration