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.
npx agentmods add commands/chrisdbaldwin/masques/audiencegit clone --depth 1 https://github.com/ChrisDBaldwin/MasquesWrote 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/chrisdbaldwin/masques/audience)<a href="https://agentmods.dev/commands/chrisdbaldwin/masques/audience"><img src="https://agentmods.dev/badge/commands/chrisdbaldwin/masques/audience.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.01753 |
| Opus 5 | $0.00007 | $0.00877 |
| Sonnet 5 | $0.00003 | $0.00351 |
| Haiku 4.5 | $0.00001 | $0.00175 |
Grade B, and why
audience scanned grade B with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -q CLAUDE_CODE_ENABLE_TELEMETRY ~/.claude/settings.json && echo "env: configured" || echo "env: MISSING" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" http://localhost:13133/ How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audience Command
The audience is the always-on observer that watches every session — masque or baseline — and scores it. Unlike a per-session summon, the audience is seated once and left running: Docker keeps the collector alive across crashes and reboots, so capture is ambient. You do not start it per session.
Arguments: $ARGUMENTS
Lifecycle (mental model)
seat ──▶ (house open, capturing every session, survives reboot) ──▶ dismiss
│
└─▶ status / logs (peek without disturbing the house)
You run seat once (first-time setup). After that the house stays open on
its own. dismiss is the rare "close the house entirely" action — you normally
leave it seated.
Instructions
Step 1: Parse Arguments
Extract the action from arguments (default: status):
seat— open the house once (start the persistent collector + verify telemetry env)dismiss— close the house entirely (stop the collector; capture stops)status— is the house open? how many sessions captured?logs— show what the audience has seen (recent collector logs)
start/stop are accepted as deprecated aliases for seat/dismiss — when
used, do the action but note the rename, because the old "start per session"
ritual no longer applies (the house stays open).
Step 2: Execute Action
Action: seat
Seat the audience once. This is setup, not a per-session step.
- Check if the audience is already seated:
docker ps --filter "name=masques-audience" --format "{{.Names}} {{.Status}}"
If it is already Up, say so and skip to verifying telemetry env (step 3) —
seating is idempotent; do not recreate a healthy house.
- If not present, seat it (build + start as a persistent, restart-on-failure service):
cd ${CLAUDE_PLUGIN_ROOT}/services/collector && docker compose up -d --build
The compose file pins restart: unless-stopped and a :13133 healthcheck, so a
crashed or hung collector is restarted automatically. Nothing leaves the
machine — the default config writes only local JSONL (see docs/otel-setup.md).
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 · 197 lines · 14 tokens per session scan B 668d82e05574
audience is a command published in the GitHub repository ChrisDBaldwin/Masques (14 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,753 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
save
Save this conversation as a new or existing reusable context.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
reset
Guided teardown of an organic-os site - what gets deregistered automatically, what you must delete or revoke yourself, and why.