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/iradoweck/antigravity-awesome-skillsnpx agentmods add skills/iradoweck/antigravity-awesome-skills/aider-delegateWrote 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/iradoweck/antigravity-awesome-skills/aider-delegate)<a href="https://agentmods.dev/skills/iradoweck/antigravity-awesome-skills/aider-delegate"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/aider-delegate/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/iradoweck/antigravity-awesome-skills/aider-delegate"><img src="https://agentmods.dev/badge/skills/iradoweck/antigravity-awesome-skills/aider-delegate.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.00033 | $0.03021 |
| Opus 5 | $0.00016 | $0.01510 |
| Sonnet 5 | $0.00007 | $0.00604 |
| Haiku 4.5 | $0.00003 | $0.00302 |
Grade A, and why
aider-delegate 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 8d 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
100% identical to aider-delegate — 0 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aider Delegate
When to Use
- You want to delegate a bounded coding task to a separate
aiderimplementer (Aider) and then review its diff yourself. - The user explicitly asked for delegation to this implementer.
You are the orchestrator. Hand a bounded coding task to a separate implementer - Aider - then review what it produced and land it yourself. You write the brief and own the judgment; Aider does the typing in its own run; you verify and commit.
The loop needs only a shell command and file access, so any comparable orchestrator can drive it.
The one thing to know about Aider
Aider commits by default. Two of its defaults would destroy the reviewable diff this skill exists to produce:
--auto-commits(defaultTrue) - Aider commits its own edits after each exchange.--dirty-commits(defaultTrue) - Aider commits your pre-existing uncommitted work before it starts editing.
The relay always passes --no-auto-commits and --no-dirty-commits, and neither is configurable
through it. If you ever drive aider by hand instead of through the relay, pass both yourself, or the
work lands as commits you never reviewed. The relay also passes --no-gitignore, because Aider
otherwise writes .aider* into .gitignore on startup and dirties the tree you are about to read.
When NOT to use this
- The task is small enough to do inline; delegation overhead is not worth it.
- The
aiderCLI is not installed, or no model is configured for it. - You want the implementer to manage its own commits. Aider can, but this skill deliberately turns that off - the diff is the deliverable.
Prerequisites (check once)
- Install Aider -
python -m pip install aider-chat, or the standalone installer from the Aider install docs. - Configure a model. Aider reads provider keys from the environment (
OPENAI_API_KEY,ANTHROPIC_API_KEY, …) or its own config; see Aider's model docs. - Confirm
aider --versionsucceeds. - Work in, or point
--cdat, the target git repository.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 228 lines · 33 tokens per session scan A d30bb1d5c001
aider-delegate is a skill published in the GitHub repository iradoweck/antigravity-awesome-skills (30 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 3,021 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aider-delegate, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.