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 skills add shinpr/nautilus --skill blueprint-standardsgit clone --depth 1 https://github.com/shinpr/nautilusWrote 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/shinpr/nautilus/blueprint-standards)<a href="https://agentmods.dev/skills/shinpr/nautilus/blueprint-standards"><img src="https://agentmods.dev/badge/skills/shinpr/nautilus/blueprint-standards/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.
<a href="https://agentmods.dev/skills/shinpr/nautilus/blueprint-standards"><img src="https://agentmods.dev/badge/skills/shinpr/nautilus/blueprint-standards.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00045 | $0.00498 |
| Opus 5 | $0.00023 | $0.00249 |
| Sonnet 5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
blueprint-standards 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 9d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blueprint Standards
Purpose
Blueprint artifacts define the structural and visual foundation that prototypes and downstream specs build upon.
They answer:
- What pages and flows exist?
- What data lives where?
- What should the product feel like?
- What concrete visual rules should AI tools reuse?
Artifact Overview
| Artifact | Question It Answers | Template |
|---|---|---|
| Information Architecture | What pages exist and how are they organized? | references/ia-template.md |
| User Flows | How do users move through the product to achieve goals? | references/flow-template.md |
| Content Model | What data types exist and how do they relate? | references/content-model-template.md |
| Brand Direction | What does the product look and feel like? | references/brand-direction-template.md |
| AI Interaction Model | How do users interact with AI features? | references/ai-interaction-model-template.md |
Relationship to Other Artifacts
docs/product/vision.md ← Strategic intent
docs/product/design-principles.md ← Trade-off resolutions
docs/product/personas/ ← Who uses it
docs/discovery/opportunities/ ← What problems to solve
docs/discovery/hypotheses/ ← What to validate
↓
docs/product/design/ ← Blueprint
↓
docs/discovery/prototypes/ ← Validation artifacts
↓
docs/prd/ ← Delivery handoff
Scope
Blueprint defines: structure, navigation, data relationships, visual direction, Visual Tokens, interaction patterns
Blueprint defers: component APIs, production-ready design systems, pixel-perfect responsive specs
Key Principles
- Opportunity-grounded: Every major page or flow traces to a real opportunity or support need
- Persona-informed: Flows and terminology reflect actual users
- Consistent across prototypes: Shared blueprint context prevents prototype-to-prototype drift
- AI-readable: Visual Tokens and decisions are written in markdown so coding agents can consume them directly
- Reusable downstream: PRDs, UI specs, and implementation can reference the same artifacts
What ships with it
5 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.
- 9d ago First seen · 56 lines · 45 tokens per session scan A 871e8ecc33e0
blueprint-standards is a skill published in the GitHub repository shinpr/nautilus (4 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 498 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
blueprint-standards
Defines structural design artifact formats — information architecture, user flows, content model, brand direction, and AI interaction model. Use when creating or reviewing structural design documents that precede prototype generation.
recipe-blueprint
Define structural design foundation — information architecture, user flows, content model, brand direction, and AI interaction model — from validated opportunities and hypotheses.
design-perspective
Integrates design principles, WCAG 2.2 AA accessibility, persona context, and state design into product decisions. Use when reviewing UX decisions, checking accessibility, applying design principles, or ensuring state coverage in acceptance criteria.
prototype-guide
Generates self-contained HTML prototypes with design context from project files. Read design principles, personas, and hypothesis files, then produce a working prototype for Usability and Value risk validation. Use when creating prototypes or validating through tangible artifacts.
recipe-refine-visuals
Optional side-workflow for design experts to refine Concrete Tokens in brand-direction.md when a named downstream consumer needs reproducible values.
productspec
Use when implementing, reviewing, planning, or changing work governed by a Product Spec. Treat .product-spec.md files as the product contract for the work.