Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add dayfinggg/openai-codex-agent-skills --skill delegategit clone --depth 1 https://github.com/dayfinggg/openai-codex-agent-skillsWrote 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/dayfinggg/openai-codex-agent-skills/delegate)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/delegate"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/delegate.svg" alt="Measured on agentmods" 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.00056 | $0.00441 |
| Opus 5 | $0.00028 | $0.00220 |
| Sonnet 5 | $0.00011 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegate
Follow the governing instructions and the user's requirements for communication, code style, authorization, and delegation. This skill supplies task-specific guidance, not permission to expand the task. Its workflow and output fields describe internal checks and relevant content, not a mandatory response layout or a progress report. When used within broader authorized work, continue that work through completion rather than stopping to deliver this skill's intermediate result.
Delegate an outcome, not a vague topic or a copy of the whole parent task.
Confirm fit
Delegate only when the user or governing instructions authorize delegation and the collaboration tools are available. This skill does not itself grant that authorization. Respect a request to work personally without subagents. Do not ask again when delegation is already authorized. The subtask must have a clear boundary, enough context to start, an observable completion condition, and no need for ongoing parent judgment. Keep work that owns shared state or final integration with the primary agent.
Write the brief
State the objective, why it matters, exact scope, inputs, relevant paths or sources, constraints, allowed side effects, expected artifact or answer, required evidence, and stopping condition. Include exclusions that prevent overlap with the parent or another agent.
When uncertainty or external dependencies can delay the lane, name their owner, an early-warning threshold, and the parent integration checkpoint. Do not let a delegated estimate silently become a parent-level commitment.
Provide raw evidence rather than the intended conclusion when the subagent is evaluating or reviewing. Do not preload a suspected answer that would bias an independent result.
Integrate
Inspect the returned evidence and artifacts. Verify claims that affect the parent outcome. Do not accept completion based only on the subagent's status message.
Output
Return or send one self-contained brief. If delegation is unavailable or prohibited by a higher-priority instruction, keep the work local rather than inventing a delegation mechanism.
What ships with it
1 file 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.
- yesterday Changed · +2 lines 5e19ea97ed0c
- 3d ago Changed · +2 lines · -1 tokens per session b66564173a8f
- 8d ago First seen · 27 lines · 57 tokens per session scan A 0523eceeba9e
delegate is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (4 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 441 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
code-review-excellence
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
architecture-design
Use only when creating new registrable ML components that require Factory or Registry patterns.
results-analysis
This skill should be used when the user asks to "analyze experimental results", "run strict statistical analysis", "compare model performance", "generate scientific figures", "check significance", "do ablation analysis", or mentions interpreting experiment data with rigorous statistics and visualization. It focuses on…
review-response
Systematic review response workflow from comment analysis to professional rebuttal writing. Use when the user asks to "write rebuttal", "respond to reviewers", "draft review response", or "analyze review comments". Improves paper acceptance rates.
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.