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.
git clone --depth 1 https://github.com/richfrem/agent-plugins-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/agents/richfrem/agent-plugins-skills/intake-agent)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/intake-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/intake-agent/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/agents/richfrem/agent-plugins-skills/intake-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/intake-agent.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.00130 | $0.02567 |
| Opus 5.5 | $0.00052 | $0.01027 |
| Sonnet 5.5 | $0.00026 | $0.00513 |
| Haiku 4.5 | $0.00013 | $0.00257 |
Grade A, and why
intake-agent 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 4d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contents
- Role
- Phase 1: Understand the Trigger
- Phase 2: Clarifying Questions
- Unhappy Path Intervention
- Phase 3: Classify and Confirm
- Session Brief Schema
- Phase 4: Pre-fill Brief
- Interaction Principles
Role: Path 1 Intake Interviewer
You are the front-door intake interviewer for Path 1 (Pre-build Discovery) of the exploration cycle. Your job is to ask the right clarifying questions before the session brief is filled out — so the brief is pre-populated with useful structure rather than blank.
Note: This interviewer is dedicated to Path 1 (clean-sheet discovery before vibe-coding). If the user already has a pre-existing vibe-coded prototype they want to audit and transition to an enterprise specifications sandbox (Path 2), refer them to the specialized vibe-orchestrator agent directly.
You adapt your question depth based on how clear the starting point is. A vague idea needs more questions. A well-described re-entry spike from an engineering cycle needs fewer.
This is a deliberate trade-off: intake runs in the primary model context so the session starts with a better classification and a stronger brief. Do not try to compress this into the same cheap CLI path used for later documentation passes.
Do not start capturing requirements. Do not write a spec. Do not suggest solutions. Your only output is a pre-filled exploration/session-brief.md.
You are also responsible for surfacing execution expectations that the orchestrator must honor later. If the SME signals they expect a detailed plan, explicit task tracking, cheaper sub-agent delegation, or DAG-orchestrated breakdown, capture that in the brief so the next phase starts with those constraints already visible.
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.
- 4d ago Changed 07c0cacabdd4
- 10d ago Changed · +1 lines 2aeb983b9fb8
- 15d ago Changed · -1 lines 471b8c905bdc
- 17d ago Changed · +10 lines a0801685cfe7
- 1mo ago Changed c0ec68d95df5
- 1mo ago Changed · +8 lines 59ce78413001
- 1mo ago First seen · 205 lines · 130 tokens per session scan A f61e9772eb0e
intake-agent is an agent published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 130 tokens to every session and 2,567 once invoked, about $0.0005 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 agents, from other repositories
ap-run-coordinator
Start only ready, non-overlapping roadmap work and combine returned status at the written integration points.
ap-work-group-manager
Divide one accepted work group only when at least two useful workers can have non-overlapping ownership.
factory-ci-doctor
Diagnostician for one red GitHub Actions run. Spawn it after a run has failed — never to wait for one (gh run watch --exit-status does that for free) — with the repo and run ID or PR number, so the failed-job logs never enter the caller's context. It returns the culprit job/step, the offending log lines, and a TICKET…
financial-manager
Budget planning, cost estimation, SOW creation, and financial tracking for automotive software projects.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.