A workflow that turns a project plan and build plan into one overview document for the coding agent. The overview records the project’s purpose and planned features in a form loaded each work session.

Use it when running the overview step of the planning workflow, before turning planned features into detailed specifications and implementation work.

It gives the agent one current source of guidance instead of making it reconstruct the project from several planning files. It also validates and normalizes the input plans first.

How aiblueprinthq/ai-blueprint configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to aiblueprinthq/ai-blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/aiblueprinthq/ai-blueprint/main/.agents/skills/overview/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/overview/github.svg)](https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/overview)

Your own site

<a href="https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/overview"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/overview/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/overview"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/overview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,472 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.03472
Opus 5.5	$0.00018	$0.01389
Sonnet 5.5	$0.00009	$0.00694
Haiku 4.5	$0.00005	$0.00347

Measured 7d ago against content hash 275dc207165e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

overview 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 7d 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.

.agents/skills/overview/SKILL.md · 283 lines

How it starts

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

overview - turn the two plans into the AI-facing source of truth

Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.

First action: Before project inspection, preflight, or any other tool call, publish running to blueprint/.state/run.json when blueprint/.state/ exists. From the project root, run the first helper that exists, node .agents/skills/blueprint-doctor/scripts/run-state.mjs or node .claude/skills/blueprint-doctor/scripts/run-state.mjs, with start --command <skill> --summary "<truthful summary>" --boundary <read-only|reviewed|local-only>. Use update at milestones, with --status blocked --resume <command> for a blocker, and finish --status ready|completed at the end; --help lists every option and blueprint/workflow.md has the full activity contract. A missing or failing helper is a warning, not a blocker.

Where this sits in the workflow:

project-plan.md  +  build-plan.md  ->  [this skill]  ->  project-overview.md  ->  /feature  ->  build
(what & why,         (high-level                          (compact product         (one spec
 written by you)      feature list,                        context loaded            at a time)
                      written by you)                      on demand)

You provide two files: blueprint/project-plan.md (what & why) and blueprint/build-plan.md (the ordered feature list), drafted directly, through any AI conversation, or with the optional /discovery skill. What matters is that you own their content. /discovery is never required. Everything else in the workflow is generated from those two. This skill is the first generation step: it distills both plans into blueprint/context/project-overview.md, the compact doc workflow skills load on demand when they need durable product context.

Input

The two planning docs, already written:

Read the full file on GitHub · 283 lines

Files

What ships with it

1 file 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.

reference/project-overview-template.md 2.1 KB

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.

7d ago Changed · +7 lines 275dc207165e
1mo ago Changed · +6 lines de809c7e9c13
1mo ago Changed · +2 lines ff0f475bef9b
2mo ago Changed · +2 lines 079cc45e224f
2mo ago Changed · +94 lines · -42 tokens per session c9dfc7fe41d0
2mo ago First seen · 172 lines · 88 tokens per session scan A c36cfbd1762d

Subscribe to this mod's changes

overview is a skill published in the GitHub repository aiblueprinthq/ai-blueprint (493 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 3,472 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-08-30.

Building agents Planning

overview next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
overviewaiblueprinthq/ai-blueprint	Skill	493	7d ago	MIT	A	46	Claude Code, 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

ai-blueprint: Skill for Claude Code