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/session-info)<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/session-info"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/session-info/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/session-info"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/session-info.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.00033 | $0.00522 |
| Opus 5 | $0.00016 | $0.00261 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
session-info 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.
What it actually says
Session Info
Report the registered work session for this conversation — the session
created via Session.Create (tobor-sessions MCP) per CLAUDE.md's FIRST ACTION
step. This is NOT the Claude Code harness/runtime; it's the NPL work session
that artifacts, tickets, and chat rooms hang off of.
1. Resolve the environment slugs
echo $NPL_ORG # organization slug (e.g. noizu-labs)
echo $NPL_PROJECT # project slug (e.g. npl)
2. Identify the active session
- If a session was already registered earlier in this conversation, use that session UUID — do not create a new one.
- If no session UUID is known yet, say so plainly: report that no work session has been registered this conversation, and note that registering one is the CLAUDE.md FIRST ACTION step. Do not silently create one just to populate this report.
When a session UUID is known, fetch its current details:
ToolCall(tool: "Session.Get", arguments: { "session": "<session-uuid>" })
(If Session.Get isn't available, use the tobor-sessions discovery tools —
ToolSearch / ToolDefinition — to find the right read tool.)
3. Output
Report as a terse definition list:
- Session GUID — the UUID
- Title — short session title
- Description — longer detail, if set
- Status — active / etc.
- Organization — slug (and name/UUID if returned)
- Project — slug (and name/UUID if returned), or
noneif the session has no project association - Created / updated — timestamps, if returned
Then a one-line reconciliation note: do the session's org/project match
$NPL_ORG / $NPL_PROJECT? Flag any mismatch (e.g. session has no project but
$NPL_PROJECT is set, or org slugs differ).
Do not invent values — report only what the tool returns and what the env
resolves to. If a field is absent, write unknown or none.
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 · 57 lines · 33 tokens per session scan A 043885afee9c
session-info is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 522 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
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.