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 skills add glichtenthal/briefing-room --skill briefing-roomgit clone --depth 1 https://github.com/glichtenthal/briefing-roomWrote 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/skills/glichtenthal/briefing-room/briefing-room)<a href="https://agentmods.dev/skills/glichtenthal/briefing-room/briefing-room"><img src="https://agentmods.dev/badge/skills/glichtenthal/briefing-room/briefing-room/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/skills/glichtenthal/briefing-room/briefing-room"><img src="https://agentmods.dev/badge/skills/glichtenthal/briefing-room/briefing-room.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.00097 | $0.02352 |
| Opus 5 | $0.00048 | $0.01176 |
| Sonnet 5 | $0.00019 | $0.00470 |
| Haiku 4.5 | $0.00010 | $0.00235 |
Grade A, and why
briefing-room 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 11d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Briefing Room
The Briefing Room turns messy context into a brief a human can think with.
The goal is not to make the input short. The goal is to make it usable. A normal summary compresses. A briefing organizes: it separates what is known from what is inferred, makes unresolved tensions visible, and gives the person a cleaner surface for judgment, creativity, planning, critique, or deeper agent work.
Use this skill when the user is overloaded by context and needs help seeing the shape of the situation.
When To Use
Use The Briefing Room when the user has enough material to organize, but the shape of the situation is not yet clear:
- scattered notes, transcripts, messages, research, or feedback
- competing interpretations of the same situation
- uncertainty about what is fact, claim, assumption, or open question
- personal or professional context that needs sensemaking before advice
- preparation for Ground Truth, The Quorum, drafting, research, planning, or human review
When Not To Use
- Use a normal summary when the user only asks for compression and no deeper structure is needed.
- Use Ground Truth when the user already has a clear claim, plan, or thesis and wants it challenged.
- Use The Quorum when the user already has a meaningful decision, trade-off, or strategy question that would benefit from multiple expert lenses.
- Use direct drafting when the user already knows the message, audience, and goal.
- Ask clarifying questions first when the input is too thin to organize without inventing context.
Core Principles
1. Organize before advising. Do not jump straight to a recommendation. First make the context legible. The user may need clarity more than advice.
2. Preserve useful complexity. Do not flatten nuance into a generic summary. Keep contradictions, minority signals, awkward details, and uncertainty if they matter.
3. Separate evidence levels. Distinguish facts, claims, interpretations, assumptions, and unknowns. This is the difference between a brief and a polished blur.
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.
- 11d ago First seen · 254 lines · 97 tokens per session scan A 8829c30c9355
briefing-room is a skill published in the GitHub repository glichtenthal/briefing-room (1 stars, last pushed 12d ago), licensed MIT. It adds 97 tokens to every session and 2,352 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
prompt-master
Generates optimized prompts for AI tools. Activates only when the user explicitly asks to write, fix, improve, or adapt a prompt for a specific AI tool (LLM, Cursor, Midjourney, image AI, video AI, coding agents, etc.). Does not activate for general conversation, coding tasks, document writing, or other…
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
github-actions-gen
A guide for creating or updating GitHub Actions workflows, which are automated jobs that test, build, release, or deploy code. It first examines the real project before choosing commands, runtimes, caches, and permissions.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.