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 athola/claude-night-market --skill delegation-coregit clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/athola/claude-night-market/delegation-core)<a href="https://agentmods.dev/skills/athola/claude-night-market/delegation-core"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/delegation-core/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/athola/claude-night-market/delegation-core"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/delegation-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 41 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 42 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 43 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 44 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 45 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00046 | $0.02237 |
| Opus 5.5 | $0.00018 | $0.00895 |
| Sonnet 5.5 | $0.00009 | $0.00447 |
| Haiku 4.5 | $0.00005 | $0.00224 |
Grade A, and why
delegation-core 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation Core Framework
Overview
A method for deciding when and how to delegate tasks to external LLM services. Core principle: delegate execution, retain high-level reasoning.
Default Posture
Delegation is on. Declining it is the step that takes a decision.
Any conjure operation, mission phase, or workflow that reaches eligible
work delegates it without being asked.
Eligible means the work is execution rather than reasoning, which the
philosophy below defines and modules/task-assessment.md classifies.
An operator who wants delegation off says so once, in one of the two
places under Declining Delegation.
This inverts the earlier framing, which listed the occasions on which to delegate and so made delegation something a caller had to remember. The occasions were correct and are now the exception list instead.
Keep Local
Delegation stops at the boundary the philosophy draws. Keep the work local when any of these hold:
- The task is reasoning: architecture, design, trade-offs, judgment.
- The prompt or context carries a secret, a credential, or data that should not leave the machine.
- The task needs iteration with the operator turn by turn.
- Correctness cannot be validated after the fact.
The first is the standing exception and covers most of what Claude does.
The rest are the red flags modules/task-assessment.md already lists.
Declining Delegation
Two switches, environment over file.
| Scope | How | Effect |
|---|---|---|
| One run | CONJURE_DELEGATION=off |
No provider is probed or spawned |
| One machine | "enabled": false in ~/.claude/hooks/delegation/config.json |
Same, until the key changes |
CONJURE_DELEGATION accepts off, 0, false, no and their
opposites, in any case.
Setting it to an on spelling re-enables delegation that the config file
turned off, so the narrower scope wins.
A disabled delegator returns a result whose fallback_reason is
delegation_disabled and spawns nothing, so opting out costs nothing.
What ships with it
7 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.
- 1mo ago Changed · -20 lines 63b4001e2419
- 1mo ago First seen · 284 lines · 46 tokens per session scan A 5580317bee6f
delegation-core is a skill published in the GitHub repository athola/claude-night-market (343 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 2,237 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
agtx-oneshot
One-shot a whole project on an agtx board: decompose the goal, run every task unattended, unblock the workers, and merge each one. Use when the user wants a long autonomous run rather than a single session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
agtx-execute
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
agtx-plan
Plan a task implementation. Analyze the codebase, create a detailed plan, write it to .agtx/plan.md, then stop and wait for user approval before making any changes.
agtx-research
Explore the codebase to understand a task before planning. Write findings to .agtx/research.md and stop. This is a read-only exploration — do not modify any files.
agtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.