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 next-actionsgit 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/next-actions)<a href="https://agentmods.dev/skills/ozzy-labs/suasor/next-actions"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/next-actions/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/next-actions"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/next-actions.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.00140 | $0.01784 |
| Opus 5 | $0.00070 | $0.00892 |
| Sonnet 5 | $0.00028 | $0.00357 |
| Haiku 4.5 | $0.00014 | $0.00178 |
Grade A, and why
next-actions 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 9d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
next-actions
未処理 task / 約束 / demand を優先度順に並べて「次にやること」を返す。順位の基線は コードが持つ（priority.list の決定論的 scorer、ADR-0041）。skill 散文で順位を決めない。
いつ発火するか
- 「次に何をする?」「やること教えて」「タスク何が残ってる?」
- 「今日やること」「今週やること」「来週やること」「優先度高いのは?」
何をするか（MCP tool flow）
read tool のみ（ADR-0004）。
-
priority.listを基線として取る（ADR-0041 決定 3 / ADR-0045）。open/in_progress な task + open commitment + un-acked demand を 1 本のランク付きリストに合成した決定論的 scorer で、同一入力に対し順序が一定になる（テストで固定）。順序モデルはコードが持つ:hard tier（開始 30 分以内の会議）> 重み付きスコア（ADR-0045）。スコアは超過日数 / 未返信日数 / demand の鮮度 / 期日接近 / 会議準備 / priority を合成する。程度が効く — 「3 週間超過」は「1 日超過」より上、期限を跨いでもスコアは下がらない
各 item は
rank/entity/id/title/reason（最も寄与した項:starting_soon/overdue/aging/unacked_demand/due_soon/prep/priority/recency）/explanation（その項の一文）/score/recordを持つ。根拠として提示するのはexplanation（「期限を 21 日超過」）であってscoreの数値ではない（ADR-0045 決定 4）。selfUserId未設定時 demand は DM のみ。 -
必要に応じ各 entity の詳細を補う（基線の順位は変えない・表示補強のみ）:
task.list（state=open/in_progress、期間指定はupdatedAfter/updatedBefore）で task のdueDate/priority/overdueを詳しく見る（ADR-0028）demand.listで demand 行のchannelName/userName（ローカル join した人間可読名・未解決はnull＝生 id fallback、ADR-0037 §10）や github notification のsource/kind（reason）を見る。提示は id ではなく名前で行う。sourceはslack/github/email（未返信スレッド・ADR-0043）/calendar（meeting_soon/meeting_prep・ADR-0044）commitment.list（state=open、direction=owed_by_meで自分が負う約束）で約束の相手/期日を見る（ADR-0021）search（mode=semantic） で各項目に関連する context を補強（embedding 無効時はsignal: embedding_disabledを見てsearch（FTS）へフォールバック、ADR-0005）
-
基線の順序に沿って next-actions を提示する。会話文脈による上書きは host の裁量（例:「今日は Slack を無視して」→ demand tier を落とす）。上書きしない限り、順位は
priority.listの基線に従う
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.
- 9d ago First seen · 58 lines · 140 tokens per session scan A cb49275bb2c1
next-actions is a skill published in the GitHub repository ozzy-labs/suasor (0 stars, last pushed 1mo ago), licensed MIT. It adds 140 tokens to every session and 1,784 once invoked, about $0.0007 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
agentrq
Lead multiple agents to accomplish big tasks with specialized workspaces/agents by assigning tasks to specialized agents.
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
agentrq
Execute tasks assigned by humans or supervisor agents within a specific AgentRQ workspace. Use when you receive channel messages or need to report progress on tasks.
bbs-relay-pickup
A coordination procedure for agents that share work on tasks through a BBS task system, where BBS is the service used to claim, run, and report task steps.
acceptance-orchestrator-v2
Acceptance Orchestrator workflow skill. Use this skill when the user needs a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention and the operator should preserve the upstream workflow, copied support files…
feishu-pm
Project Management skill for Feishu Bitables. Add tasks, list records, and track progress directly from the agent.