agy-worker
Use when Codex or Claude Code should delegate repository exploration or implementation to Google Antigravity CLI (agy), then review, verify, repair, and deliver the result.
Install / Use
npx skills add aiskillstore/marketplace --skill agy-workerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of agy-worker
agy-worker scores 85/100 on our quality scale, 2748th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 13 KB long, split into 4 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
It has 428 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so agy-worker is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-12. Automated pattern scan on 2026-11-12. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
agy-worker compared with similar skills
All 4 of these similar skills score higher than agy-worker; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| agy-worker (this skill)by aiskillstore | 85 | 428 | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
Frequently asked questions
- How do I install agy-worker?
- Run
npx skills add aiskillstore/marketplace --skill agy-worker. The install tabs above show the steps for each supported agent. - Which AI agents does agy-worker work with?
- It is written for Claude Code and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is agy-worker safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is agy-worker still maintained?
- The repository was last updated about 2 months ago, so agy-worker is actively maintained.
Skill content
View source on GitHubname: agy-worker description: Use when Codex or Claude Code should delegate repository exploration or implementation to Google Antigravity CLI (agy), then review, verify, repair, and deliver the result. license: MIT compatibility: "OpenAI Codex CLI and Claude Code. Requires Bash, Python 3, git, and agy with provider network access." metadata: author: cagdasyurekli version: "0.26.2"
Delegate repository work and verify the result
Delegate substantive exploration or implementation to agy, then inspect its diff
and run driver-owned checks. Unknown files, architecture or a first test command do
not prevent useful exploration; worker envelopes are not evidence.
SKILL_ROOT contains this file. In Claude Code it is ${CLAUDE_SKILL_DIR},
substituted in instructions rather than exported by Bash. Resolve the package:
PIPELINE="$(bash "$SKILL_ROOT/scripts/resolve-pipeline.sh")" || exit $?
Use "$PIPELINE/doctor.sh" --repo /absolute/path/to/target for offline readiness;
ready proves neither authentication nor task success. See the Package README.
Authorize provider work
Obtain human approval for the task, exact provider-readable content, transmission and isolation modes, caller-selected model and budget. One upfront approval may cover predictable same-scope repairs and mechanical digest refresh. New scope, content exposure, destination, isolation, permissions or budget needs fresh authority. SHA values bind the documented controller inputs, not the entire human decision; refreshing a still-applicable binding is not another approval request. Goal and hand-authored JSON are not ordinary-use prerequisites.
Prefer --provider-scope FILE --approve-transmission-sha SHA256 for bounded jobs. It binds reviewed read entries, their content digest, and a write subset in a fresh owner-private mode-0700 Gitless stage.
Whole-worktree dispatch requires --approve-whole-worktree LAUNCH_APPROVAL_SHA256. Every disposable-worktree entry is provider-readable and may reach Google/Gemini; --add-dir, prompt denylists and gate path policies do not narrow that read boundary.
Neither workflow.sh run nor the advanced agy-worker.sh initial dispatch has an implicit transmission mode or an implicit --provider-isolation.
The whole-worktree digest binds content, kinds, full file mode bits, symlink target hashes, the
readable manifest, provider isolation and native grant profile. The scoped digest
binds canonical read/write policy, readable path/kind manifest, selected bytes and
executable bits, isolation and grant profile; scoped mode rejects symlinks and does
not bind full POSIX permissions. The controller rechecks the approved boundary
before provider start. The human approves one launch_approval_sha256 over canonical
launch_authority: those content inputs, destination and Git base, exact normalized
task and constructed prompt, fixed transport templates, workflow/edit mode, model/effort,
cycles and time budgets, scoped repair, self-verification manifest digest, provider-env
names, slash policy, additional directories and provider schema digest. Preview the
exact task and all launch options; reuse them unchanged for the approved run. Only
trailing LF bytes are removed from UTF-8 task input; spaces and CRLF are preserved.
Environment values and private verification commands are never serialized into the
approval payload. Use the private prelaunch review checklist
in Project lifecycle and verification, including any optional self-verification
commands, IDs and limits; keep that manifest out of the provider preview and prompt.
Retired dispatch and workflow job formats are rejected; finish or discard them with their creating release, without migration.
--provider-isolation session|native is caller-owned with no implicit value: the driver names the mode and its consequence in the approval request and never selects session on its own. session uses the existing AGY session with normal user filesystem/network authority plus ambient HOME, enabled user plugins, hooks and MCP servers; staging and reconciliation are not host isolation.
The controller compares a bounded observation of the verified main source checkout
against one immutable job baseline before later launches and before candidate
admission or retention. No-candidate failures and cancellations without a report
defer the post-exit comparison until the next launch; a cancelled repair defers it
until its inherited candidate is next used. A detected change blocks
the candidate; ignored untracked files and writes elsewhere on the host are outside
this check. The main-workdir helper skips this comparison, while public launch
preview still requires a linked disposable worktree. See
Security and compatibility.
Explicit --provider-isolation native requires supported macOS scoped containment; it never falls back to session mode. Preserve the recorded isolation mode and grant profile across repairs.
Provider-scope approval grants neither provider execution, Git action, driver acceptance, nor publication.
Exclude secrets, denied paths and unrelated private content from every approved entry; telling the worker not to read an approved entry is not a control.
Keep raw logs and controller state outside the worktree and prompts. Each launch requires capability preflight and immediate executable-binding recheck. Model and effort stay caller-owned. Child environment opt-ins require approval per variable name. Installation grants no provider or Git authority.
Read Security and compatibility before a first
live dispatch or changing execution exposure. It owns native network/Keychain limits (native needs a one-time dedicated agy keychain),
verifier environments and no-follow boundaries. AGY 1.4.2 was observed starting workspace MCP commands from .agents/, _agents/, .agent/ and _agent/. Preview rejects known
executable configuration under all four roots. Each launch checks actual cwd ancestry in
both modes. Prefer scoped mode excluding it, then a disposable worktree without it;
ancestors must be clear. Session mode can start enabled user-plugin MCP servers and run
global and enabled-plugin hooks in headless mode with slash commands disabled; hooks can
observe or rewrite tool calls, including shell commands. The guide details reserved paths,
native plugin/hook exclusion evidence and limits. Read the required
launch notices
before initial, resume, continue or restart attempts; notices do not repeat approvals.
Choose and run the workflow
| Intent | Workflow | Cycle budget | Driver action |
|---|---|---|---|
| Explore, understand, review or plan | explore | default 2, allowed 1..2 | Spot-check findings; state coverage limits. |
| Bounded feature, refactor or tests | task | default 2, allowed 1..2 | Review the diff; run relevant checks. |
| Project build or broad audit-and-fix | project | default 5, allowed 1..5 | Review changes; run build, tests and lint. |
Select only needed files and direct tests, name exact files/functions and the expected change, size the budget to that scope, and split large changes into bounded jobs. See the maximum-runtime observation and cleanup test.
Use workflow.sh run --preview, approved run, read-only status, and verify-finalize; the facade does not choose a model, assurance, repair or external action.
Project lifecycle and verification owns copyable commands, Verification v2 candidate bindings and recovery.
Quick path: save the reviewed scope file outside the target repository with mode 0600, then run the facade with a unique job ID:
TARGET=/absolute/path/to/approved-repository
JOB_ID=job-12345
SCOPE=/absolute/private/provider-scope.json
TASK='the exact approved bounded task'
"$PIPELINE/workflow.sh" run --preview --repo "$TARGET" --job-id "$JOB_ID" --provider-scope "$SCOPE" --provider-isolation session --task "$TASK"
This creates the disposable worktree and private state. Review launch_approval_sha256,
then repeat the same command without --preview, adding
--approve-transmission-sha "$LAUNCH_SHA". A minimal owner-private
scope file, with entries sorted by path, is:
{"schema_version":1,"kind":"agy-worker-provider-scope","read":[{"path":"src/parser.py","kind":"file"},{"path":"tests","kind":"tree"}],"write":[{"path":"tests","kind":"tree"}]}
Use paths that exist in the reviewed worktree and keep the scope file outside it
with mode 0600. The facade derives an owner-private state path for later
status and verify-finalize; see the linked guide for the complete sequence.
Run driver-selected build/test commands and Python imports in an isolated
verification copy with PYTHONDONTWRITEBYTECODE=1. Inspect the bound candidate's
actual diff and gate binding directly. Never manually edit, delete, or chmod the
bound candidate; send needed
repairs to the same worker conversation. Never execute an envelope's
commands_run or tests_run; bind only sanitized driver findings to the candidate.
Gate and verify-finalize --verify-argv verifiers run in the bound candidate: choose
only commands known to be read-only there. Snapshot rejection detects changes to bound candidate state
after they happen; it does not isolate the candidate. Verifiers run untrusted
candidate code with the user's authority; the gate does not detect changes outside
the candidate, including Git hooks and configuration. Feed separate copy test results
into Verification v2.
Repair observable failures in the same conversation within budget; never silently
fall back to direct-driver work after provider failure or exhausted budget.
Use initial --allow-scoped-repair for approved multi-turn scoped work. Without that
grant, a changed scoped candidate is result/finalize-only. Preserve useful work;
restart requires an explicit user decision.
Self-verification is optional advisory feedback, not acceptance. An unknown first
check is not a hard stop. Reuse checks only for unchanged candidate bytes and relevant
environment; the driver independently decides the final assurance.
For trust-boundary changes, use the short design note and independent review in
Material planning governance.
Explicit delegation-first requires running the delegation-policy.sh evaluator before substantive repository work.
Controller records are local: the runtime cannot infer prior work or approval and
must never silently authorize direct-driver fallback after missing approval, a hard
stop, preflight/provider failure or exhausted budget.
Claude Code: in non-interactive claude -p or SDK runs, dispatch in the foreground
(up to the host's ten-minute ceiling) or keep the turn alive until it finishes;
never end the turn while a job runs. In interactive sessions, a long dispatch may
use Bash run_in_background: true while the main session remains active. Do not
duplicate a job or treat a Bash timeout as provider failure.
Bash permission approval is separate from transmission approval. Read
Claude Code host operation.
Hard stops and delivery
Stop for missing exact approval; secrets or denied/unrelated private content in
approved inputs; writes escaping the worktree, entering .git or traversing symlink
boundaries; or unapproved Git, publication, installation, account or external actions.
Never use dangerous permission/approval-bypass flags or disable the host s
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
