blueprint-sync

blueprint-sync is a skill for Claude Code from DanialDaeHyunNam/omniscitus. It costs 55 tokens per session (1,054 once invoked), scanned A, original, MIT.

A project-file synchronizer for keeping `.omniscitus/blueprints/` records aligned with the files on disk.

In plain words
What is it for?
Use it to scan a project, update blueprint records, and migrate an older single blueprint file into the newer directory layout.
Why use it?
It catches files that were created but not recorded, marks files that were deleted, and fills in missing purposes so the blueprint does not become stale.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the omniscitus plugin — 16 skills, 3 hooks shipped together

Good fit Use it to scan a project, update blueprint records, and migrate an older single blueprint file into the newer directory layout.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/danialdaehyunnam/omniscitus/blueprint-sync
Install

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.

Any agent
npx skills add DanialDaeHyunNam/omniscitus --skill blueprint-sync
Clone the repo
git clone --depth 1 https://github.com/DanialDaeHyunNam/omniscitus

Made for: Claude Code.

Or install omniscitus, the plugin that ships this one along with the rest of its 16 skills, 3 hooks.

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 blueprint-sync

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/danialdaehyunnam/omniscitus/blueprint-sync"><img src="https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/blueprint-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,054 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.01054
Opus 5 $0.00028 $0.00527
Sonnet 5 $0.00011 $0.00211
Haiku 4.5 $0.00006 $0.00105

Measured 12d ago against content hash 5b71cce61a88, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

blueprint-sync 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 12d 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.

plugins/omniscitus/skills/blueprint-sync/SKILL.md · 132 lines

How it starts

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

Blueprint Sync — Detect Untracked Files

Scan the project filesystem and sync .omniscitus/blueprints/ with reality. Finds user-created files that hooks missed, marks deleted files, and fills empty purpose fields.

When to Use

  • User types /blueprint-sync
  • User says "sync blueprints", "파일 동기화"
  • You notice blueprints might be stale

Instructions

Step 1: Check Prerequisites

If .omniscitus/blueprints/ directory doesn't exist, create it:

mkdir -p .omniscitus/blueprints

Migration: If a legacy .omniscitus/blueprints.yaml (single file) exists, migrate it:

  1. Read and parse the single file
  2. Group entries by top-level directory (root-level files → _root)
  3. Write each group to .omniscitus/blueprints/{dir}.yaml
  4. Delete the legacy .omniscitus/blueprints.yaml

Step 2: Scan Filesystem

Use git ls-files to get all tracked (non-ignored) files. This automatically respects .gitignore at all levels (root and nested):

git ls-files --cached --others --exclude-standard \
  | grep -v '^\.omniscitus/' \
  | sort

If not a git repo, fall back to:

find . -type f \
  -not -path "./.git/*" \
  -not -path "./node_modules/*" \
  -not -path "./.omniscitus/*" \
  -not -path "./.next/*" \
  -not -path "./dist/*" \
  -not -path "./build/*" \
  -not -path "./__pycache__/*" \
  -not -path "./.vercel/*" \
  -not -name "*.lock" \
  -not -name ".DS_Store" \
  | sort

Step 3: Compare with Blueprints

Read all .omniscitus/blueprints/*.yaml files. Merge them into a single map for comparison.

Blueprint file mapping rule: A file's blueprint is determined by its top-level directory:

  • src/utils/auth.tsblueprints/src.yaml
  • plugins/omniscitus/server.jsblueprints/plugins.yaml
  • README.md (root-level) → blueprints/_root.yaml

For each file on disk:

Not in any blueprint → New user-created file. Add to the correct per-directory blueprint with:

  • status: active
  • source: user:{git user.name} (run git config user.name to get the identity)
  • created: from git log --format="%ai" --diff-filter=A -- "{file}" | tail -1 or today
  • purpose: ""
  • change_count: from git log --oneline -- "{file}" | wc -l

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

  1. 12d ago First seen · 132 lines · 55 tokens per session scan A 5b71cce61a88

Subscribe to this mod's changes

blueprint-sync is a skill published in the GitHub repository DanialDaeHyunNam/omniscitus (5 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,054 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-31.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens