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/npl-update-subs-doc)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/npl-update-subs-doc"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/npl-update-subs-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/npl-update-subs-doc"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/npl-update-subs-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.00919 |
| Opus 5 | $0.00000 | $0.00460 |
| Sonnet 5 | $0.00000 | $0.00184 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
npl-update-subs-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 4d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SUBS.md — Maintenance Guide
Purpose
docs/SUBS.md maps the repo's git submodules and subtrees: path, purpose, stack, and coupling (which other modules it depends on or interacts with). It lets agents and developers answer "where does X live and what does it touch" without opening each repo.
It supersedes the "Registered submodule index" table in Portfolio/OVERVIEW.md — do not double-maintain that table; OVERVIEW keeps placement policy only.
Structure
docs/
├── SUBS.md # Main submodule map (grouped tables)
└── SUBS.summary.md # One-line-per-group index for agents
Sources of Truth
Unlike PROJ-LAYOUT (directory scan), submodule data comes from git metadata:
git config -f .gitmodules --get-regexp 'submodule\..*\.path' # registered set
git submodule status # SHA + drift + missing
Then enrich each entry with: purpose/stack (repo README, mix.exs/package.json presence) and coupling (evidence sources below).
Content Schema
Per module:
| Field | Rule |
|---|---|
| Path | As registered in .gitmodules, relative to repo root |
| Purpose | One concise phrase — what it is, not how it works |
| Stack | Only when obvious (Elixir / Next.js / Rust / Swift / static / MCP) |
| Coupling | Other submodules/subtrees it depends on or interacts with. Mark (D) documented (OVERVIEW.md, .infra-config.yaml, docs/) vs (I) inferred |
Group tables by top-level area (Apps, WebApps, Libs, Utilities, Games/…, repo-root subtrees). Maintain the coupling clusters list at the top (e.g. NPL ecosystem, Libs→apps, Utilities↔terraform) — these are the high-value navigation hints.
Known-coupling evidence sources, in priority order: .infra-config.yaml (shared namespaces/tiers/liquibase targets), Portfolio/OVERVIEW.md, docs/arch/*, repo READMEs, path/name heuristics (last resort, always (I)).
Size Limits
| Location | Target Size | Action When Exceeded |
|---|---|---|
| SUBS.md | < 250 lines | Split group tables to subs/{group}.md, leave group + summary row |
| Purpose text | 1 line | Details belong in the module's own README |
| Coupling column | ≤ 4 targets | Link to a cluster instead of enumerating |
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.
- 4d ago First seen · 83 lines · 0 tokens per session scan A 5257eb7d713c
npl-update-subs-doc is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 919 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-07.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.