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/.claude/commands/update-layout-v2.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/commands/noizu-labs-ml/noizupromptlingo/update-layout-v2)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/update-layout-v2"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/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/commands/noizu-labs-ml/noizupromptlingo/update-layout-v2"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/update-layout-v2.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.00048 | $0.00620 |
| Opus 5 | $0.00024 | $0.00310 |
| Sonnet 5 | $0.00010 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
update-layout 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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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: ... -->
Update:
- Tree diagrams (regenerate)
- File listings (add new, remove deleted)
- Path references
- Examples with current file names
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.
- 7d ago First seen · 108 lines · 48 tokens per session scan A 596f90c2da75
update-layout is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 620 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-09-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.