Official AI Agent Plugins & Skills Marketplace for Antigravity (AGY), Claude Code, and Cursor
Agent
Delegate to this subagent when you need changeset@2 artifacts produced from a git diff. Input is a git diff, optionally a linked spec@1, and optionally smith's criteriaevidence from the TDD run that produced this diff. A diff spanning multiple independent topics produces one changeset@2 per topic, never one bundled…
Agent
Delegate to this subagent when the user has staged git changes and needs a conventional commit message written. Input is the staged diff. The agent reads shared/references/conventional-commits.md for type and scope conventions. Output is a JSON object containing commitmessage, type (feat, fix, docs, style, refactor…
Agent
Delegate to this subagent when the user needs a pull request title and body written for a set of staged or committed changes. Input is a git diff and optionally a linked spec@1 or requirement@1. The agent reads the PR template from shared/references/github.md and writes from the reviewer's perspective — what does a…
Agent
Delegate to this subagent when you need a release-artifact@2 generated from a collection of changeset@2 entries. Input is a list of changeset@2 JSON objects, the prior released version string, and a release date in YYYY-MM-DD format. Each input changeset already carries consumerimpact and semverimpact, set at…
Agent
Delegate to this subagent before a PR is opened, to assemble the complete review package for the reviewer. Input is the changeset diff, optionally a linked spec@1 or requirement@1, test results, and any open questions the author wants answered. The agent bundles these into a structured review package — diff summary…
Agent
Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…
Agent
Delegate to this subagent when the user wants to create a new plugin from scratch. Provide a plugin ID and a description of what it should do. Generates a complete, ready-to-install plugin directory: plugin.json, a skills/ /SKILL.md with a 100-200 word CSO description, one stub agent file per declared agent using the…
Agent
Delegate to this subagent when the user wants to design a new JSON Schema for an inter-agent artifact — a structured payload passed between producers and consumers in the plugin ecosystem. Provide a description of what the artifact represents, who produces it, and who consumes it. The designer produces a JSON Schema…
Agent
Delegate to this subagent when you have a completed requirement@1 (or free-text design intent) and need a formal component spec@1 drafted. Input is a requirement@1 and optionally design references (mockup description, existing component family, design-system tokens). Output is a spec@1 conforming to…
Agent
Delegate to this subagent when a component spec@1 needs a definitive pass/fail judgment before entering the planning phase. Input is a spec@1 JSON object describing a UI component. This is an adversarial gatekeeper — the default disposition is fail, and the spec must earn a pass. The spec passes only if all four…
Agent
Delegate to this subagent when a plan@1 needs adversarial review before any implementation begins. Input is a plan@1 JSON object and its source spec@1 (read from specfilepath if set). The agent checks eight dimensions: acceptance criteria in the spec with no corresponding task (missing), tasks referencing symbols not…
Agent
Delegate to this subagent when a plan@1 exists and you need a rough effort estimate before committing to execution. Input is a plan@1 JSON object. The agent produces a per-task time estimate in minutes, marks each task as parallelizable or sequential, lists blocking dependencies by task ID, and produces a totalminutes…
Agent
Delegate to this subagent when you have a completed spec@1 and need a sequenced, executable implementation plan. Input is a spec@1 (or its specfilepath, read from disk if provided). Output is a plan@1 conforming to shared/schemas/[email protected], with specfilepath and spechash propagated from the spec. Decomposes into…
Agent
Invoke once per candidate after scanner (and boundary-tracer for T7 or T10 candidates). Never batch multiple candidates in a single invocation. Input is one candidate@1 entry and the recon manifest; for T7 or T10 candidates, also receives the field survival map from boundary-tracer. The agent reads actual code at the…
Agent
Conditional agent invoked only when scanner produces candidates classified as T7 (write-only fields or intent-capture discard) or T10 (error downgrade). Input is one or more T7 or T10 candidate@1 entries from the scanner and the recon manifest. For Rust workspaces, the agent loads shared/references/rust-hazards.md…
Agent
Invoke before any ranger scanning begins. Input is a workspace root path. This agent detects the primary language by inspecting Cargo.toml (rust) or package.json (typescript or javascript) at the workspace root. It identifies entry points such as binary crates, main.ts, or exported index files, then traces imports and…
Agent
Invoke after recon has produced a workspace manifest. Input is the manifest from recon (including livefiles and language) and optionally a specific hazard focus category. For Rust, the agent loads shared/references/rust-hazards.md; for TypeScript or JavaScript, it loads shared/references/typescript-hazards.md. It…
Agent
Delegate to this subagent when ranger has produced a finding-report@1 and the defect class requires a structural fix — a change to the architecture, type system, interface boundary, or abstraction layer — rather than a patch of individual bug instances. Input is a finding-report@1. Output is a spec@1 conforming to…
Agent
On-demand diagnostic: given a specfilepath and a workspace root, verifies the current code still implements every acceptance criterion in the spec. Reads the spec from disk, not from context, and reads implementation/tests from the workspace. When a prior changeset@2's criteriaevidence is available, uses its pointers…
Agent
Delegate to this subagent when you need to verify that a draft spec@1 is grounded in its source artifacts — the requirement@1 and optional research-report@1 — before it proceeds to auditing or gating. Input is a spec@1 draft plus the originating requirement@1 and any research-report@1 used to produce it. For each…
Agent
Delegate to this subagent to execute exactly one task from a plan@1 via the full TDD cycle. Input is a single task object from a plan@1, a workspace manifest from recon, and optionally precisiontests from mutator. When specfilepath is set, reads the task's coverscriteria acceptance criteria from that file before…
Agent
Delegate to this subagent after implementer commits and before exit-gate runs. Input is the workspace manifest from recon and the list of files touched by implementer in the current task cycle. The agent detects the workspace language (Cargo.toml → rust uses cargo-mutants; package.json → typescript/javascript uses…
Agent
Delegate to this subagent after a implementer task commits and before exit-gate runs. Input is the set of commits from a completed implementation task, the original task specification, and the workspace manifest (which carries the language field). The agent loads the language-specific hazards reference (rust-hazards…
Agent
Delegate to this subagent after recon produces a source map. Input is the source map from recon plus the original research question. The agent reads every identified source and extracts findings relevant to the question, with a citation, confidence level (confirmed, likely, or assumed), and source attribution for…