Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Agent Action Proof — Verify MCP Writes

    1

    Check whether one MCP update landed before retrying it. Get the observed result and the next safe action.

    Free

    1 useSecurity scanned
    Agent Action Proof — Verify MCP Writes

    Agent Action Proof — Verify MCP Writes

    Example session with this skill installed

    Synthetic local demonstration; no connected account or provider is used. The task-store fixture was created for this example and is not part of the skill package.

    Use Agent Action Proof to move task T-42 in workspace North from Doing to Ready. I authorize that single change. The supplied task-store contract supports read(workspace, id) and update(workspace, id, status, expected_revision, request_id); the initial revision is 1. It will lose the acknowledgement after committing the update. Read the task back before deciding whether another write is needed. Report the actual result and retry decision.

    • Read your context and instructions
    • Compiled the agent action proof

    Task update completed — no retry needed

    Actual synthetic local run, 21 October 2026 at 05:09:10 UTC. No MCP server or live task service was contacted.

    ReceiptObserved value
    TargetNorth / T-42
    BeforeDoing, revision 1
    Requested resultReady
    Update requestsynthetic-request-001, expected revision 1
    Tool responseAcknowledgement lost after the local commit
    Target readbackReady, revision 2
    OutcomeCompleted in the local fixture
    Write calls / resulting mutations1 / 1
    Retry writes0

    The readback found the requested status on the intended task. There is no outstanding change to repeat.

    The companion boundary run made readback unavailable after the same lost acknowledgement. Its outcome stayed

    unknown, with zero retry writes. An already-Ready fixture required zero writes.

    Next step: retain this receipt with the task. For a real provider, use its current tool contract and authoritative readback; this local example does not establish that provider's behavior.

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

    About this skill

    Your agent updates a task. The request times out. You need to know whether to retry, because another write could repeat a change that already happened.

    Agent Action Proof follows one authorized action from its starting state to a checked result. Before the call, it confirms the target, current tool contract and intended change. After the call, it reads the target system and compares what happened with what you asked for.

    A result you can act on

    You receive a short action receipt: the target, before and after values, request identity, readback time and retry decision. If the change is already present, the agent can finish without another write. If the evidence is inconclusive, the receipt says what must be checked next.

    Use it for an issue update, document edit or other connected-tool change where an acknowledgement alone leaves doubt.

    This free package contains instructions for your agent. Bring the connected tool, access to the exact target and authorization for the change; provider integrations and credentials are supplied by your environment. Some services cannot provide timely readback or safe retries. Those outcomes remain unknown.

    Ask your agent to verify one specific change and name the result you expect.

    Covers one specifically authorized tool action and its observed target state.
    Provider contract, timely readback and safe retry semantics depend on the connected service.
    Inconclusive evidence stays unknown; exactly-once delivery, universal rollback and unobserved effects are not guaranteed.
    No provider integration, credentials, scripts or MCP server are bundled.

    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

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    • Free with an Agensi account

    Permissions

    Network Access

    Access to the user's already authorized connected tool and readback source for a real action. No default account access or external write comes from the package.

    Listed1 month ago
    Updated24 days ago

    What's inside

    Frequently Asked Questions

    The exact target, the change you authorize, the expected result and access to the current write/readback tools. The agent checks the live tool contract before acting.

    Only when the target system or documented operation handle supplies enough evidence. Otherwise it records an unknown outcome and the next check, without a blind retry.

    A focused SKILL.md workflow and agent metadata. Your host supplies the connected tools and credentials. The synthetic task-store fixture in the listing demonstrates the workflow; it is author-side evidence.

    New in Agents & Orchestration