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 ozzy-labs/suasor --skill briefgit clone --depth 1 https://github.com/ozzy-labs/suasorWrote 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/ozzy-labs/suasor/brief)<a href="https://agentmods.dev/skills/ozzy-labs/suasor/brief"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/brief/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/ozzy-labs/suasor/brief"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/brief.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.00145 | $0.02276 |
| Opus 5.5 | $0.00058 | $0.00910 |
| Sonnet 5.5 | $0.00029 | $0.00455 |
| Haiku 4.5 | $0.00015 | $0.00228 |
Grade A, and why
brief 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 2mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
brief
状況サマリの単一入口（ADR-0046）。期間 × 読み手 × 観点の 3 つで振る舞いを決める。read-only。
以前は personal-brief / catchup / weekly-review / external-brief / health-check の 5 本に分かれていたが、ユーザーから見ればすべて「まとめて」であり、違うのはパラメータだけだった（「今週どうなってる」の一言で 5 本が競合していた）。
いつ発火するか
| 言いかた | period | audience | focus |
|---|---|---|---|
| 「今日のまとめ」「最近どう」「自分の状況」 | 24h（既定） | self | summary |
| 「前回以降の差分」「久しぶりに確認」「不在中の動き」 | 前回確認時刻から | self | summary |
| 「週次レビュー」「棚卸し」「今週やり残したこと」 | 7d | self | review |
| 「上司向け週次報告」「クライアント向け進捗」「外向きステータス」 | 指定期間 | external | summary |
| 「健全性チェック」「今どれくらい溜まってる」「数値で」 | 現在 | self | numbers |
明示がなければ period=24h / audience=self / focus=summary。
対象を指定しない「前回から何が変わった」もここ（period=前回確認時刻から）。対象資料・PR を指定した「この資料は前回から何が変わった」は source-review（target=diff）が受ける。
何をするか（MCP tool flow）
すべて read tool（ADR-0004）。副作用なし・エージェント自律 OK。
1. パラメータを決める
- period — ISO 8601（offset 付き）の
sinceを作る。「前回以降」はホスト側が保持する seen-marker（最終確認時刻）をsinceにする（専用の MCP tool は無い。状態はホストが持つ） - audience —
self（既定）/external（上司・顧客向け。tone と粒度が変わる） - focus —
summary（何が動いたか）/review（未完・約束・滞留の棚卸し）/numbers（件数のスナップショット）
2. focus 別に読む
focus=summary（既定）
brief（since/until）で期間バンドルを取る（要約文は生成しない＝ADR-0006 の ML 委譲。組み立てはホスト LLM）。open commitment もバンドルに入る（非時間軸・緊急度順・#513）ので、commitment.listを別途叩く必要はない- 補強が要れば
priority.list（いま何が優先か）/task.list（updatedAfter）/decision.list（recordedAfter）/inbox.list（state=open）/demand.list（observedAfter）/search（トピック関連 context）
focus=review（棚卸し）
task.list（state∈{open,in_progress}+ overdue 抽出）— 未完commitment.list（双方向）— 自分が負う / 相手が負う約束inbox.list（state=open）— 滞留brief（since=7d）— 期間の動き- 落ちている項目を明示する。状態遷移そのものは
task-update/inbox-triage/commitment-reviewskill へ HITL で橋渡しする（ここでは書かない）
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.
- 2mo ago First seen · 101 lines · 145 tokens per session scan A 7b6c67ab1c6a
brief is a skill published in the GitHub repository ozzy-labs/suasor (0 stars, last pushed 2mo ago), licensed MIT. It adds 145 tokens to every session and 2,276 once invoked, about $0.0006 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
OpenSourceManagement
Triages open issues, pull requests and GitHub Discussions across the principal's own open-source repos (the list in Config.md) via the gh CLI, ranks what needs attention with suggested replies, posts edit-in-place marker comments, diffs new Ollama library models against a local model box, and takes a private repo…
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
cs-escalation-brief
Redacta un informe de escalada estructurado para una cuenta de cliente en riesgo. Úsalo cuando una cuenta haya escalado, cuando un cliente amenace con cancelar, cuando un problema de cliente P1 requiera atención ejecutiva, o cuando prepares un plan de retención interno. Produce un informe de escalada preciso con…