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.
git 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)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/update-layout"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/update-layout/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"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/update-layout.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.00803 |
| Opus 5 | $0.00000 | $0.00402 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00080 |
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 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
update-layout - Persona
Type: Command Category: Documentation Automation Version: 1.0.0
Overview
The update-layout command synchronizes project layout documentation with the actual codebase structure. It automatically detects structural changes (new directories, removed files, reorganizations) and updates docs/PROJECT-LAYOUT.md accordingly while preserving manually-added descriptions, annotations, and custom sections. This ensures layout documentation remains accurate without losing valuable human-authored context.
Purpose & Use Cases
- Post-refactoring sync - Update documentation after major code reorganization or directory structure changes
- Quarterly review - Periodic refresh to catch accumulated drift between filesystem and documentation
- Initial documentation - Generate comprehensive PROJECT-LAYOUT.md for new projects
- CI/CD validation - Verify documentation accuracy in automated pipelines
- Framework migration - Adapt layout documentation when upgrading frameworks or changing architectural patterns
Key Features
✅ Smart merge strategy - Preserves user annotations while updating structural elements
✅ Framework detection - Adapts section names and conventions based on detected framework (Rails, Django, Phoenix, Next.js, Express)
✅ Four-phase workflow - Load → Scan → Update → Validate for comprehensive accuracy
✅ Annotation preservation - Maintains <!-- user: --> markers and custom sections through updates
✅ Change detection - Identifies new/removed/reorganized directories and files automatically
✅ Spec compliance - Generates documents following project-layout-spec.md with all 11 required sections
Usage
# Agent invocation
@npl update-layout
# Validation only (dry-run)
@npl update-layout --validate
The command reads the current filesystem structure, compares it against existing documentation, merges changes while preserving annotations, and outputs an updated docs/PROJECT-LAYOUT.md with a change summary showing new/removed entries.
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 · 79 lines · 0 tokens per session scan A 214103c3b016
update-layout is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 803 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.