ai-blueprint: Skill for Codex

.agents/skills/discovery/SKILL.md

discovery is a skill for Codex from aiblueprinthq/ai-blueprint. It costs 54 tokens per session (1,613 once invoked), scanned A, original, MIT.

A guided planning conversation for exploring a software project before writing detailed project and build plans. It is optional and can take multiple turns.

In plain words
What is it for?
Use it when you explicitly want a discovery process that eventually drafts blueprint/project-plan.md and blueprint/build-plan.md after you approve the drafts.
Why use it?
It helps clarify goals, requirements, and trade-offs when the project needs more thought before implementation.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is aiblueprinthq/ai-blueprint's own configuration. It tells Codex how to work on ai-blueprint itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-blueprint configures →

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/discovery/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint

Made for: 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 discovery

README.md
[![agentmods](https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/discovery/github.svg)](https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/discovery)
Your own site
<a href="https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/discovery"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/discovery/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 discovery

Your own site · 80×15
<a href="https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/discovery"><img src="https://agentmods.dev/badge/skills/aiblueprinthq/ai-blueprint/discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,613 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 71
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.01613
Opus 5 $0.00027 $0.00807
Sonnet 5 $0.00011 $0.00323
Haiku 4.5 $0.00005 $0.00161

Measured 7d ago against content hash 25b1bd03ffe3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

discovery 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/discovery/SKILL.md · 173 lines

How it starts

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

discovery - develop the plans through a deep conversation

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 using the dashboard activity contract in AGENTS.md.

Where this can sit in the workflow:

/onboard  ->  write the plans directly  ->  /overview
          \
           ->  [discovery]  ->  review and approve plan drafts  ->  /overview

/discovery is an optional planning partner, not a required workflow gate and not a quick questionnaire. It can span as many turns as the project needs. Its job is to help the user think through the product, preserve the depth and nuance of that conversation, and draft the two user-owned planning files only when the user asks for drafts.

Running /onboard never starts this skill. Empty plans never require it. A user who writes detailed plans manually, has another AI conversation, or arrives with finished plans continues directly to /overview exactly as before.

Step 1 - establish the starting point

Read only the planning and project facts needed for the conversation:

  • blueprint/project-plan.md
  • blueprint/build-plan.md
  • the root project manifest, README, and framework configuration when they already contain relevant facts
  • blueprint/context/project-overview.md only when the user is revisiting an established project's direction

Classify each planning file as a template, partial draft, or substantive plan. Never treat existing user content as disposable. When either plan has real content, summarize what it already establishes and ask whether the user wants to deepen it, revise a specific direction, or use it unchanged as conversation context. Do not replace it with a fresh generic plan.

Start with a short working hypothesis about the project and name the most important unknown. Then ask one focused question. Do not draft either plan yet.

Read the full file on GitHub · 173 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.

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. 7d ago Changed · +2 lines · -65 tokens per session 25b1bd03ffe3
  2. 11d ago First seen · 171 lines · 119 tokens per session scan A e009a594eff4

Subscribe to this mod's changes

discovery is a skill published in the GitHub repository aiblueprinthq/ai-blueprint (393 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,613 once invoked, about $0.0003 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-30.

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens