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-state-of-the-union-docs)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/npl-update-state-of-the-union-docs"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/npl-update-state-of-the-union-docs/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-state-of-the-union-docs"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/npl-update-state-of-the-union-docs.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.01076 |
| Opus 5 | $0.00000 | $0.00538 |
| Sonnet 5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
npl-update-state-of-the-union-docs 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROJ-SOTU.md — Maintenance Guide
Purpose
docs/PROJ-SOTU.md is a dated state-of-the-union snapshot of the component: where it currently is, what works great, what has improved since the last major cluster of changes, what it still needs, and the opportunities and threats ahead — including positioning/marketing notes. It is the document a stakeholder reads to decide invest, use, or wait.
Unlike ARCH/LAYOUT (timeless descriptions), SOTU is perishable by design — every statement is true as of its date.
Structure
docs/
├── PROJ-SOTU.md # Current snapshot only (keep small)
├── PROJ-SOTU.summary.md # Companion: status line + top 3 points per section
└── sotu/
├── 2026-03-02.md # Archived prior snapshots, verbatim
└── ...
Section Template
# State of the Union — {component}
**As of:** YYYY-MM-DD **Maturity:** {level} **Trajectory:** {rising|steady|declining|dormant}
## Status at a Glance
[2-4 sentences: what this is, where it stands, the headline since last SOTU]
## What Works Great
[Bulleted, specific, verifiable — features earning their keep]
## Improved Since Last SOTU
[Changes landed since the previous snapshot's date; cite the change cluster,
link CHANGELOG.md milestones if present]
## Needs / Gaps
[Missing pieces, debt, known weaknesses — honest, prioritized]
## Opportunities
[What becomes possible next: features, integrations, users it could serve]
## Threats / Risks
[What could erode it: upstream drift, bitrot, superseding tools, bus factor]
## Positioning
[1 short paragraph: who it's for and the one-line pitch — marketing-usable]
## Next
[The 2-5 things most worth doing, in order]
Maturity Scale
Use exactly these levels so cross-component comparison works:
| Level | Meaning |
|---|---|
| experimental | Exploring; may be abandoned; no stability promise |
| alpha | Works for the author; sharp edges expected |
| beta | Works for teammates; gaps known and listed |
| stable | Daily-driver; changes are deliberate |
| mature | Feature-complete; changes are rare and conservative |
| legacy | Superseded or in maintenance-only; note the successor |
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 · 114 lines · 0 tokens per session scan A f03681926b25
npl-update-state-of-the-union-docs 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 1,076 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.