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 ashermahonin/agentic-skills --skill intake-coordinatorgit clone --depth 1 https://github.com/ashermahonin/agentic-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/ashermahonin/agentic-skills/intake-coordinator)<a href="https://agentmods.dev/skills/ashermahonin/agentic-skills/intake-coordinator"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/intake-coordinator/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/ashermahonin/agentic-skills/intake-coordinator"><img src="https://agentmods.dev/badge/skills/ashermahonin/agentic-skills/intake-coordinator.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.00066 | $0.00430 |
| Opus 5.5 | $0.00026 | $0.00172 |
| Sonnet 5.5 | $0.00013 | $0.00086 |
| Haiku 4.5 | $0.00007 | $0.00043 |
Grade A, and why
intake-coordinator 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 2mo 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.
What it actually says
Intake Coordinator
Purpose
Turn an unclear request into a working brief without making the user repeat themselves. Preserve urgency, remove fog, and create just enough structure for the next skill to act confidently.
Inputs
- Extract the user goal, desired outcome, deadline pressure, and emotional priority.
- Separate facts from assumptions.
- Identify what can be decided now and what genuinely needs clarification.
- Ask only the smallest number of questions needed to unblock the next phase.
Decision process
- Write a one-paragraph brief in plain language.
- List success criteria as observable outcomes, not slogans.
- Mark constraints: time, budget, stack, security, data, deployment, design, and ownership.
- Define non-goals so the task does not quietly expand.
- Name the next skill and the artifact it should produce.
- If the request is narrow and safe, hand off quickly instead of over-planning.
Decision boundaries
- Use Context7 MCP for current library, framework, platform, API, CLI, and configuration documentation whenever the task depends on external technology behavior.
Decision record
- Request brief
- Assumptions and open questions
- Success criteria
- Constraints and non-goals
- Next recommended skill
Ready when
- The brief should feel like the user was understood, not processed.
- Do not invent requirements to avoid asking a necessary question.
- Do not ask questions whose answer can be found in the repo or existing docs.
- Keep the next step concrete.
Handoff
Hand off a concise brief plus the exact uncertainties the next skill must resolve.
References
references/brief-template.md: Use this template for01-request-brief.mdand02-clarifications.md.
What ships with it
2 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.
- 2mo ago First seen · 54 lines · 66 tokens per session scan A 5e6df50b8734
intake-coordinator is a skill published in the GitHub repository ashermahonin/agentic-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 430 once invoked, about $0.0003 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-08-31.
intake-coordinator compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| intake-coordinatorashermahonin/agentic-skills | Skill | 10 | 2mo ago | MIT | A | 66 | Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |