A read-only way to investigate an idea against the actual codebase before deciding to build it. It examines relevant code, tests, project files, and existing plans without changing files.

Use it to compare implementation approaches, check whether a feature such as caching would help, and discuss trade-offs before planning work.

It helps reveal whether a proposed change fits the current system, what alternatives exist, and where uncertainty remains. It avoids writing a plan or specification before the basic question is understood.

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/explore/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/explore/github.svg)](https://agentmods.dev/skills/aiblueprinthq/ai-blueprint/explore)

Your own site

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

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

When invoked 848 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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.00848
Opus 5.5	$0.00023	$0.00339
Sonnet 5.5	$0.00011	$0.00170
Haiku 4.5	$0.00006	$0.00085

Measured 1mo ago against content hash bf1488f48719, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

explore 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 1mo 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/explore/SKILL.md · 78 lines

How it starts

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

explore - investigate an idea before deciding to build

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.

Explore is a read-only conversation grounded in the actual project. It can help with questions such as whether caching would help a dashboard, whether teams belong in the product, or which upload approach fits existing code.

No plans or active feature are required. Do not require /overview, invent a plan, or treat missing Blueprint context as a blocker to discussing the idea. This command never writes activity state, including blueprint/.state/run.json.

Start from the question

Use the supplied topic or relevant conversation context. With neither, ask what the user wants to investigate. For a vague idea, state a tentative interpretation and ask a focused question only when its answer changes the investigation.

Reuse context already loaded in the session. Read relevant project instructions, code, tests as text, manifests, and existing plans when they help answer the question. Follow the actual implementation far enough to support your claims; point to concrete files or symbols. Avoid scanning unrelated parts of the repo. Read-only Git inspection can establish what exists or is already in progress.

Authoritative documentation lookup is appropriate when technical uncertainty needs it. Distinguish documented facts from what this project actually uses. Missing code or evidence is an uncertainty to explain, not permission to execute an experiment or to invent current behavior.

Discuss the options

Keep the conversation proportional to the question. Compare plausible options against the user's needs and existing project constraints. Include doing nothing when the current behavior may already be sufficient. Do not invent scale, security requirements, or new abstractions to justify a change.

Explain the strongest case against your recommendation and how confident you are. Separate observed facts, assumptions, and unanswered questions. Say what evidence could change the recommendation without gathering it through execution. An unresolved question or a recommendation to leave the project alone is a valid outcome.

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

1mo ago First seen · 78 lines · 57 tokens per session scan A bf1488f48719

Subscribe to this mod's changes

explore is a skill published in the GitHub repository aiblueprinthq/ai-blueprint (493 stars, last pushed 7d ago), licensed MIT. It adds 57 tokens to every session and 848 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-09-14.

Planning

explore next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
exploreaiblueprinthq/ai-blueprint	Skill	493	7d ago	MIT	A	57	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