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-doc.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-doc)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/update-layout-doc"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/update-layout-doc/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-doc"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/update-layout-doc.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.00000 | $0.01380 |
| Opus 5 | $0.00000 | $0.00690 |
| Sonnet 5 | $0.00000 | $0.00276 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
update-layout-doc 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- npl-update-layout-doc — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROJ-LAYOUT.md — Maintenance Guide
Purpose
docs/PROJ-LAYOUT.md provides a navigable map of the project structure with concise descriptions of what each directory and key file contains. It helps developers quickly locate code and understand organization.
Structure
docs/
├── PROJ-LAYOUT.md # Main project tree (keep small)
└── layout/
├── src.md # Detailed breakdowns by directory
├── config.md
├── scripts.md
└── ...
What to Include
Include
- All directories
- Key files (entry points, configs, READMEs)
- Special dotfiles:
.envrc,.env.example,.editorconfig,.nvmrc, etc. - Files that must be manually configured
Exclude
- Files matched by
.gitignore(node_modules, build outputs, caches) - Generated files
- IDE-specific files (unless team-standardized)
Exception Dotfiles to Always Document
.envrc # direnv configuration
.env.example # environment template
.editorconfig # editor settings
.nvmrc / .node-version / .tool-versions
.dockerignore
.prettierrc / .eslintrc.*
flake.nix / shell.nix
Content Guidelines
Tree Format
project-root/
├── src/ # Application source code
│ ├── api/ # HTTP handlers
│ └── core/ # Business logic
├── config/ # Configuration files
├── scripts/ # Build and utility scripts
├── .envrc # direnv — loads environment
└── README.md # Project entry point
Description Rules
- One-line descriptions, right-aligned or on same line
- Focus on what it contains not how it works
- Use consistent terminology
- Mark required-to-configure files clearly
Size Limits
| Location | Target Size | Action When Exceeded |
|---|---|---|
| PROJ-LAYOUT.md | < 150 lines | Extract sections to layout/ |
| Directory listing | < 10 items | Collapse with summary + link |
| layout/*.md files | < 100 lines | Consider further decomposition |
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 · 176 lines · 0 tokens per session scan A a6b088dda736
update-layout-doc is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,380 tokens. 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.