Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add YoungjaeDev/my-claude-plugins/plugin install devWrote 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/youngjaedev/my-claude-plugins/new)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/new"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/new.svg" alt="Measured on agentmods" 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.00167 | $0.01431 |
| Opus 5 | $0.00084 | $0.00715 |
| Sonnet 5 | $0.00033 | $0.00286 |
| Haiku 4.5 | $0.00017 | $0.00143 |
Grade A, and why
new 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 today.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dev new skill
Day-1 bootstrap for an empty project directory. Same orchestration as the /dev:new command — both surfaces gate on the preflight guard before ANY destructive op.
Step 0 — Preflight hard guard (NON-NEGOTIABLE)
Run this before any other body content. It refuses to run in a non-empty directory. The model MUST NOT skip this block, MUST NOT rewrite it to a softer check, and MUST surface the abort message verbatim if the guard fires.
# Hard guard — refuses to run if cwd contains ANYTHING beyond ignorable OS junk.
# Walks up to 5 levels deep so deeper sources (e.g. src/app/main.py) and any
# top-level file (Dockerfile, Makefile, .env, docs/*) trigger the abort. Only
# .git/ and OS metadata (.DS_Store, Thumbs.db, desktop.ini) are pruned.
FIRST_EXISTING=$(find . -mindepth 1 -maxdepth 5 \
\( -name '.git' -o -path './.git/*' \
-o -name '.DS_Store' -o -name 'Thumbs.db' \
-o -name 'desktop.ini' \) -prune \
-o -print 2>/dev/null | head -1)
if [ -d .git ] || [ -n "$FIRST_EXISTING" ]; then
echo "[abort] dev:new refuses to run in a non-empty directory."
echo " cwd: $(pwd)"
echo " Existing entry detected: ${FIRST_EXISTING:-.git/}"
echo " If you really want to add Claude/Codex scaffolding to an existing"
echo " project, use /docs:write-rules or /wiki:bootstrap-wiki"
echo " instead."
exit 1
fi
Windows / non-POSIX hosts: the guard above is POSIX shell. On Codex CLI / Claude Code where the default shell is PowerShell, wrap it:
bash -c '<guard>'(Git Bash, WSL, or any POSIX shell on PATH). The intent — refuse to proceed if cwd has any content beyond.git/and OS metadata — must be honored regardless of how the check is invoked.
If the guard passes, proceed to the run record, then the full procedure.
Step 0.5 — Run record (state-envelope v0)
The run record (state-envelope v0) is opened by the shared procedure, not here: its open + per-phase record_step mechanism lives once in references/new-procedure.md (Phase 0.5), so this skill and the /dev:new command record identically. Follow that Phase 0.5 block — do not re-inline the jq here. Convention + schema: .claude/rules/state-envelope.md (concept mirror in this repo's AGENTS.md). The record lives under gitignored .claude/state/, is kept out of the Phase 6 commit by the Phase 6 .gitignore seed, and is orthogonal to .claude/state/spec.json (owned by dev:state-tracker) — different file, different concern.
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.
- today First seen · 71 lines · 167 tokens per session scan A 30eb7d053ac3
new is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 167 tokens to every session and 1,431 once invoked, about $0.0008 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-09-05.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…