agentmods.dev

packet-intake

packet-intake is a skill for Claude Code, Codex from Justinmendezai/The-Adam-Repo. It costs 74 tokens per session (1,073 once invoked), scanned A, original, Apache-2.0.

An intake process for a project packet, which is a folder describing a planned build. It checks the packet's required information and asks the operator to resolve open decisions before research and implementation begin.

In plain words
What is it for?
Use it to validate PACKET.md, record missing information, inspect referenced files and folders, and create notes for the research-and-planning stage.
Why use it?
Missing requirements or unclear success conditions can cause an automated build to head in the wrong direction. Resolving those questions at the start reduces interruptions and ambiguous decisions later.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

not rated 12repo +1 18d ago A scan 74 tokens original Apache-2.0

Good fit Use it to validate PACKET.md, record missing information, inspect referenced files and folders, and create notes for the research-and-planning stage.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/justinmendezai/the-adam-repo/packet-intake
View source ↗ Justinmendezai/The-Adam-Repo justinmendez.ai
Install

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.

Any agent
npx skills add Justinmendezai/The-Adam-Repo --skill packet-intake
Clone the repo
git clone --depth 1 https://github.com/Justinmendezai/The-Adam-Repo

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for packet-intake

README.md
[![agentmods](https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/packet-intake/github.svg)](https://agentmods.dev/skills/justinmendezai/the-adam-repo/packet-intake)
Your own site
<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/packet-intake"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/packet-intake/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.

agentmods 80×15 button for packet-intake

Your own site · 80×15
<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/packet-intake"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/packet-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,073 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.01073
Opus 5 $0.00037 $0.00536
Sonnet 5 $0.00015 $0.00215
Haiku 4.5 $0.00007 $0.00107

Measured 12d ago against content hash 78b81845273a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

packet-intake 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 12d 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.

skills/packet-intake/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

packet-intake

The orchestrator's first move on every project. Validate the packet, grill the operator until decisions are resolved, write what you learned, then hand off to research-and-plan.

This is the one required upfront session with the operator. It front-loads judgment so the team can build without you for the rest of the run. Do not grill mid-build — no ambiguities during slice dispatch; those should have been resolved here.

Skip grilling only when packet.orchestration.require_intake_grilling: false or adam.json has "require_intake_grilling": false (emergency/hotfix paths only).

Inputs

  • Path to a packet folder (default: packet/ in the project repo) or a PACKET.md.
  • The packet schema at ~/adam/packet/schema.json.

Steps

  1. Read PACKET.md frontmatter and validate against schema.json.

    • Missing required keys → list them and stop until the operator provides them or explicitly defers in open_questions.
    • Empty success_criteria → blocking. We need testable outcomes.

  2. Walk refs/, data/, schemas/, examples/ if present. List every file. Note its path. Do not read large files yourself — log them for research-and-plan to dispatch a subagent against.

  3. Sanity check tech_context.repo_path.

    • Does the path exist? Is it a git repo? On what branch?
    • Log dirty repo or feature-branch state in intake notes. Surface to operator during grilling if it affects scope.

  4. Surface ambiguities. Read each goal and success criterion:

    • Could two engineers read this differently?
    • Is the user-visible behavior concrete?
    • Could you write a failing test for it today?

    For each ambiguity, draft a question. Do not invent answers — that's what grilling resolves.

  5. Required grilling pass. Before the first question, give the grill-me preamble (why this interview exists). Then run grill-with-docs on the union of:

    • The packet's open_questions
    • Your discovered ambiguities

Read the full file on GitHub · 73 lines

Changes

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.

  1. 12d ago First seen · 73 lines · 74 tokens per session scan A 78b81845273a

Subscribe to this mod's changes

packet-intake is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,073 once invoked, about $0.0004 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.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens