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 tmusser/context-to-action-skills --skill brief-megit clone --depth 1 https://github.com/tmusser/context-to-action-skillsWrote 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/tmusser/context-to-action-skills/brief-me)<a href="https://agentmods.dev/skills/tmusser/context-to-action-skills/brief-me"><img src="https://agentmods.dev/badge/skills/tmusser/context-to-action-skills/brief-me/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/tmusser/context-to-action-skills/brief-me"><img src="https://agentmods.dev/badge/skills/tmusser/context-to-action-skills/brief-me.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.00017 | $0.00607 |
| Opus 5.5 | $0.00007 | $0.00243 |
| Sonnet 5.5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
brief-me 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 1mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brief-me
Purpose
Turn messy connected or pasted context into a short conversation-state brief the user can act on quickly.
Use For
- "What did I miss?"
- "Brief me before this meeting."
- "What changed since Monday?"
- "What needs my response?"
Inputs
- Slack
- Gmail
- Calendar
- Zoom transcript
- Atlassian
- Hex or other data output
- Pasted notes
- Any combination of the above
- A
reduce-to-factsledger or conversation-state record
Optional Operator Setup
brief-me works without setup. When the user wants recurring briefs tailored to
how they operate, use the bundled OPERATOR_PROFILE.md
flow.
An operator profile may tune prioritization, compression, section order, terminology, meeting-prep behavior, and when suggested replies appear. It must not change source truth, confidence, unresolved gaps, or authorization boundaries.
- Opt in; never require setup before producing a useful brief.
- Do not infer preferences from connected data when the user has not stated them.
- Treat the user's current request as higher priority than profile defaults.
- If no profile is available, use the standard output contract below.
Guardrails
- Read before write.
- Do not send messages, create events, update tickets, or publish outputs unless explicitly asked.
- Separate source-backed facts from assumptions and suggestions.
- Prefer small source windows.
- Surface source gaps.
- Do not dump raw transcript content by default.
- Keep the output workplace-user friendly.
Portable Output Contract
- Use only the useful subset of source-backed facts, assumptions, source gaps, stakeholder sensitivities, potential misreads, and the suggested next action.
- Use the smallest useful output.
- Label assumptions and preserve source gaps, source anchors, and confidence labels.
- When consuming upstream state, do not promote an assumption, inference, open question, proposed action, or stakeholder position into a fact, decision, commitment, owner, or deadline without new source support.
- Keep unresolved approvals, owners, timing, and blockers explicit in the brief.
- Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +20 lines 94e589fa5c44
- 1mo ago First seen · 71 lines · 17 tokens per session scan A e8ccbe97f8de
brief-me is a skill published in the GitHub repository tmusser/context-to-action-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 607 once invoked, about $0.0001 per session on Opus 5.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
eisenhower-matrix
"What is important is seldom urgent and what is urgent is seldom important." Master Dwight D. Eisenhower's prioritization framework to focus on what truly matters. Use when: Feeling overwhelmed by too many tasks and not enough time; Weekly planning to set priorities for the week ahead; Daily triage when everything…
time-energy-management
Manage PM time and energy across competing demands without burning out or dropping critical work. Covers prioritization of PM activities, calendar discipline, and sustainable pace. Use when overwhelmed by meetings, losing time to reactive work, or when important strategic work keeps getting pushed.
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…
technical-debt-register
Documenta y prioriza un backlog de deuda técnica con impacto empresarial, estimaciones de esfuerzo y estrategia de resolución. Úsalo cuando se te pida auditar deuda técnica, crear un registro de deuda, priorizar deuda técnica para un trimestre, documentar atajos arquitectónicos o construir una hoja de ruta de…
cs-health-scorecard
Construir un cuadro de mando de salud del cliente para una cuenta específica. Úsalo cuando te pidan calificar la salud de la cuenta, evaluar el riesgo de renovación, construir un panel de salud o evaluar la probabilidad de que una cuenta se renueve o expanda. Produce un cuadro de mando de salud estructurado con estado…
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…