Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/keli-wen/agy-staffnpx agentmods add skills/keli-wen/agy-staff/agy-implementerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/keli-wen/agy-staff/agy-implementer)<a href="https://agentmods.dev/skills/keli-wen/agy-staff/agy-implementer"><img src="https://agentmods.dev/badge/skills/keli-wen/agy-staff/agy-implementer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/keli-wen/agy-staff/agy-implementer"><img src="https://agentmods.dev/badge/skills/keli-wen/agy-staff/agy-implementer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00081 | $0.01084 |
| Opus 5.5 | $0.00032 | $0.00434 |
| Sonnet 5.5 | $0.00016 | $0.00217 |
| Haiku 4.5 | $0.00008 | $0.00108 |
Grade A, and why
agy-implementer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 20d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
86% identical to implementer — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agy implementer
Hand a coding task to the agy staffer. agy edits the real working tree under its unrestricted permission profile; the companion is a thin launcher and job collector. Pass the user's requested delivery through in the task text instead of doing Git work yourself.
Locating the companion
This skill file lives at <plugin-root>/opencode-skills/agy-implementer/SKILL.md; resolve the companion path relative to this skill directory:
node "<skill-dir>/../../companion/agy-companion.mjs" implement [flags] --prompt "task description"
Pass the user's task description verbatim via --prompt; use --prompt-file <path> or --stdin for long text.
[!IMPORTANT] Run this command unsandboxed — agy needs a localhost port and its OAuth token file, which harness sandboxes hide. In Codex, request escalated permissions for the command. Details:
../agy-jobs/references/troubleshooting.md. (The companion passes--dangerously-skip-permissionsto agy in this mode — that is the unrestricted profile working as designed.)
Workspace and delivery
- Inside a git repository, dirty workspaces are allowed. When
git status --porcelainis not clean, the companion injects a bounded pre-run status summary into the implement prompt so agy treats those paths as user-owned context. - Outside a git repository the companion warns that agy's edits cannot be reviewed or rolled back via git, and proceeds. Relay that warning; there is no diff to fall back on.
- By default, agy leaves a working-tree diff. If the user explicitly asks for a commit, push, or PR, include that request verbatim in the task text and let agy do that exact Git delivery.
- After the run, surface agy's summary and the current workspace state. Do not add your own commit/PR step unless the user separately asks you to do it.
Collecting the result
The command returns a job id. Read ../agy-jobs/SKILL.md for result collection and recovery: dispatch, wait for the final result, then validate as needed. Do not proactively observe progress, read logs or inspect intermediate artifacts while running. Observe only when the user explicitly asks for progress; diagnose a failure or a result requiring intervention under the jobs protocol.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 20d ago Changed · -2 tokens per session ac8abf3c7c07
- 1mo ago Changed 44ba91539bc6
- 1mo ago Changed · -2 lines c13c2f56fca7
- 1mo ago First seen · 59 lines · 83 tokens per session scan A 27b15301a256
agy-implementer is a skill published in the GitHub repository keli-wen/agy-staff (772 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 1,084 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to implementer, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
conductor-revert
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.
pr-review
Review pull requests and Git diffs with Graph-It-Live risk, breaking-change, dependency-impact, cycle, unused-export, and test-candidate evidence. Use when asked to review a PR, inspect a diff, assess merge risk, check a branch before merging, create a Graph-It-Live review gate, or explain review-pr results. Trigger…
atlas-changelog
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
cc-commit-msg
A workflow for generating structured Git commit messages, which are short records describing changes made to a codebase.
pr-review
Comprehensive code review for pull requests using parallel multi-agent analysis. Audits CLAUDE.md compliance, checks for bugs, analyzes git history, reviews comments, and filters by confidence score. Use when reviewing a GitHub PR, mentions "code review", "review this PR", or "/code-review".