Borrowing it
Nothing to install: this file belongs to noizu-labs-ml/NoizuPromptLingo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/noizu-labs-ml/NoizuPromptLingo/main/.agents/skills/source-command-update-layout-v2/SKILL.mdgit clone --depth 1 https://github.com/noizu-labs-ml/NoizuPromptLingoWrote 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/noizu-labs-ml/noizupromptlingo/source-command-update-layout-v2)<a href="https://agentmods.dev/skills/noizu-labs-ml/noizupromptlingo/source-command-update-layout-v2"><img src="https://agentmods.dev/badge/skills/noizu-labs-ml/noizupromptlingo/source-command-update-layout-v2/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/noizu-labs-ml/noizupromptlingo/source-command-update-layout-v2"><img src="https://agentmods.dev/badge/skills/noizu-labs-ml/noizupromptlingo/source-command-update-layout-v2.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00657 |
| Opus 5 | $0.00026 | $0.00329 |
| Sonnet 5 | $0.00010 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
source-command-update-layout-v2 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 5d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-update-layout-v2
Use this skill when the user asks to run the migrated source command update-layout-v2.
Command Template
Update Layout Documentation
Refresh docs/PROJECT-LAYOUT.md to reflect current directory structure while preserving user annotations.
NPL Dependencies
Load NPL definitions before proceeding using the NPLLoad MCP tool:
NPLLoad(expression="syntax fences")
Workflow
Phase 1: Load Existing Documentation
- Read
docs/PROJECT-LAYOUT.md(if exists) - Extract user annotations (descriptions, comments, notes)
- Identify custom sections not in standard template
Phase 2: Scan Current Structure
Generate fresh directory tree and file inventory:
# Get directory structure
tree -L 3 -d --noreport
# Get key files
find . -maxdepth 3 -type f \( -name "*.md" -o -name "*.json" -o -name "*.yaml" -o -name "*.toml" -o -name "Makefile" -o -name "Dockerfile" \) | head -50
Cross-reference with existing documentation to identify:
- New directories/files to document
- Removed items to clean up
- Reorganized structure to update
Phase 3: Update Documentation
Directory Structure Overview:
- Regenerate tree diagram
- Preserve existing annotations where structure unchanged
- Add annotations for new directories
Layer Breakdowns:
- Update each layer section with current files
- Preserve file purpose descriptions
- Add new files, remove deleted ones
Key Files:
- Refresh entry points table
- Update configuration file list
- Preserve "Edit When" guidance if still accurate
Naming Conventions:
- Verify patterns still match reality
- Update examples with current file names
Quick Reference:
- Update "Finding Files" paths
- Add new common search patterns
Phase 4: Validate
- Verify all referenced paths exist
- Check tree diagrams match actual structure
- Confirm naming conventions are accurate
- Ensure no orphaned references
Merge Strategy
Preserve:
- User-added file descriptions
- Custom annotations on directories
- Additional sections not in template
- Notes marked with
<!-- user: ... -->
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.
- 5d ago First seen · 114 lines · 52 tokens per session scan A 53b758034fbe
source-command-update-layout-v2 is a skill published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 657 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-09-04.
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…
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…
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…
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…
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…