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 agentmods add skills/yankieldbc2/codex-skills-library/codex-project-intakenpx skills add YankielDBC2/codex-skills-library --skill codex-project-intakegit clone --depth 1 https://github.com/YankielDBC2/codex-skills-libraryWrote 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/yankieldbc2/codex-skills-library/codex-project-intake)<a href="https://agentmods.dev/skills/yankieldbc2/codex-skills-library/codex-project-intake"><img src="https://agentmods.dev/badge/skills/yankieldbc2/codex-skills-library/codex-project-intake.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 | $0.00030 | $0.00539 |
| Opus 5 | $0.00015 | $0.00269 |
| Sonnet 5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
codex-project-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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Project Intake
Goal
Turn a fresh or inherited repository into a clear working system with the right project docs, state files, risk notes, and next step, while minimizing token waste and dead ends.
When to use
Use this skill when you need to start a project from scratch, rescue an existing one, or re-establish control after the repo has drifted.
When not to use
Do not use this skill for a tiny isolated change when the relevant files are already obvious.
Inputs
AGENTS.mdand any nested agent instructions.docs/CODEBASE_INDEX.mdor the closest equivalent.docs/CODEX_STATE.md,docs/PLANS.md, anddocs/DECISIONS.mdif they exist.- The package manifest, entry points, and top-level folder scan.
docs/EFFICIENCY_SYSTEM.mdandtemplates/project/EFFICIENCY_RUN.jsonfor large or ambiguous work.
Workflow
- Detect the repo root and read project instructions before editing.
- Identify stack, package manager, major folders, and command surface.
- Decide whether the repo is a fresh bootstrap or an in-progress takeover.
- Create or update the project index, state, plan, and decision files.
- For new projects, establish the minimal operating scaffold and confirm the first safe task.
- For existing projects, map the current shape, identify drift, and choose the smallest useful recovery step.
- If the work is large or uncertain, run the efficiency benchmark workflow to compare baseline and treatment.
- Validate only what the change touches.
- Report what changed, what remains risky, and what to do next.
Quality bar
- The next action must be obvious after the intake pass.
- The repo should end with a durable state, not just a chat summary.
- The plan should be small enough to execute and specific enough to avoid wandering.
- The user should know whether the repo is ready to start work or needs recovery first.
Validation
- Run the narrowest useful validation for the files changed.
- Run benchmark comparison commands when efficiency claims are involved.
- Run secret scanning and artifact checks when instructions, templates, or examples changed.
What ships with it
4 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.
- 5d ago First seen · 59 lines · 30 tokens per session scan A 6c735cd4d721
codex-project-intake is a skill published in the GitHub repository YankielDBC2/codex-skills-library (10 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 539 once invoked, about $0.0002 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
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
n8n:human-like-code-review
Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.
n8n:create-pr
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
n8n:reproduce-bug
Reproduce a bug from a Linear ticket with a failing test. Expects the full ticket context (title, description, comments) to be provided as input.