wavves

    1

    Parallel agent loops with saved state and shared constraints.

    $50

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    wavves

    Example session with this skill installed

    /wavves charter a lane named docs-sweep for the public docs refresh and run a first /mod-check on the written plan

    • Read your context and instructions
    • Compiled the wavves

    The moderator chartered lane docs-sweep and wrote waveset.md under the lane home. Parallel runners in a /mod-check wave reviewed the written plan, then returned blockers along with gaps to the moderator. The moderator left the build step unstarted during the open review wave.

    The moderator chartered lane docs-sweep and wrote waveset.md

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

    About this skill

    What's included

    Workflow skills

    wavves skills and blank templates sit in the package. The README keeps product keep-terms with their plain meaning.

    • A lane is one stream of work with its own folder. The moderator charters the lane in the lane file waveset.md through /charter.
    • A wave is one round of parallel agents in a lane. The moderator numbers waves from W1 up in the charter file waveset.md.
    • The moderator is the thread the user talks in. Waves go out from the moderator and grades come back.
    • Through /mod-check the moderator runs a read-only review wave against a written plan. The moderator locks the open calls with /mod-decide after that review.
    • Through /mod-rotate the moderator hands a heavy thread over to the next moderator term in a rotation file. Moderator term ids look like r02.
    • Through /mod-kick the moderator starts a kick, which is a move to another machine with a published allowlist and a short paste.
    • The moderator keeps lane status in the registry file registry.yml.
    • Through /layover the moderator audits a multi-root workspace. Through /shrug the moderator carries out the recommended actions.

    /remeasure

    Through /remeasure the moderator turns an agent's "done" into a gate with a claim and a check someone else can rerun. JSON and log evidence lands on disk in gate-captures. A grade comes from someone other than the author. A run of the bundled script on a JSON capture returns a rejection for self-grading along with missing fields and placeholder evidence. Sixty validation cases stay out of the sold package so a buyer runs the script on real captures. Missing or changed hashed artifacts fail under that script. Work item and lineage field formats get a confirm in the same run. Gate records of a wavves lane take their own field names like wave or verdict under the --wavves option.

    Pickup check

    On pickup the next moderator term runs the pickup check in /mod-rotate. One script tests claimed commits against local git. The same run looks for claimed file paths on disk. A second check covers the JSON work registry. A fix row for messages in the output of either script sits in five recovery playbooks. On pickup the moderator also remeasures the JSON and log evidence saved in gate-captures for what the orchestration agent completed.

    Rotation history audit

    In /mod-rotate the next moderator term runs a rotation history audit across the rotation files in a repo in order. Gaps in the numbering and breaks in the chain of terms get an ERROR line. The same run also flags rotation files a later term deleted along with claimed commits missing from git and claimed paths missing from disk. One fix row per message sits in a reference along with a manual check for work without the script. Rotation files accept audit in the header form from /mod-rotate as well as in the plain field form.

    Inside the /mod-rotate reference the registry and rotation guide cover how to keep a registry and a numbered rotation history so the next moderator term can check earlier claims on pickup. A step-by-step rotation section covers what a rotation file records and how to stamp commits with the term name. A buyer also learns where to save the check output at pickup and why older rotation files never change.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    Scripts in the wavves package need Python 3 and a local git binary on the machine that runs them. Secret handling through /set-key is built for macOS Terminal.app on the machine that holds the secret. Through /layover the moderator keeps a multi-root repo audit read-only. The run writes only the layover report.

    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 buying a skill.

    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

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 20 days ago

    Software
    PythonGitjestNode.js

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access

    Scripts in the wavves package need Python 3 and no other packages. Pickup commit checks and rotation history audit runs also need a local git binary. Optional network use is limited to the gap-probe script when a run polls HTTP endpoints during a measured transition.

    Listed24 days ago
    Updated20 days ago

    What's inside

    Frequently Asked Questions

    Through the moderator a user charters lanes, so long-horizon campaigns run as waves with state saved on disk. An orchestration agent runs the waves in the background with runners on the scoped execution-layer work. The next moderator term hydrates from files on disk with nothing carried over in the context window.

    Through /remeasure the moderator turns a done claim from a worker into a gate with a runnable check. On disk under gate-captures the run saves JSON evidence along with log evidence for the gate. A second person grades the capture, with the author of the claim kept off the grade.

    Scripts in the wavves package need Python 3 and no other packages. Pickup commit checks and rotation history audit runs also need a local git binary. Secret handling through /set-key is built for macOS Terminal.app on the machine that holds the secret.

    Through /mod-rotate the moderator hands a heavy thread over to the next moderator term in a rotation file. On pickup the next moderator term runs the pickup check against the rotation file. The same term also remeasures the JSON and log evidence saved in gate-captures.

    New in Agents & Orchestration