agentmods.dev

slack-triage

slack-triage is a skill for Claude Code, Codex from ozzy-labs/suasor. It costs 168 tokens per session (1,763 once invoked), scanned A, original, MIT.

A workflow for collecting and organising unresolved Slack mentions and direct messages. Slack is a team messaging app; the workflow can turn selected messages into tasks, decisions, inbox items, or reply drafts with user approval.

In plain words
What is it for?
Use it to gather unhandled mentions and DMs, sort them by type and urgency, create follow-up candidates, and mark items as handled or dismissed.
Why use it?
It removes the need to scan Slack manually for messages that still need action and keeps follow-up work from being missed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 0repo 1mo ago A scan 168 tokens original MIT

Good fit Use it to gather unhandled mentions and DMs, sort them by type and urgency, create follow-up candidates, and mark items as handled or dismissed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ozzy-labs/suasor/slack-triage
View source ↗ ozzy-labs/suasor
Install

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.

Any agent
npx skills add ozzy-labs/suasor --skill slack-triage
Clone the repo
git clone --depth 1 https://github.com/ozzy-labs/suasor

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for slack-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/ozzy-labs/suasor/slack-triage/github.svg)](https://agentmods.dev/skills/ozzy-labs/suasor/slack-triage)
Your own site
<a href="https://agentmods.dev/skills/ozzy-labs/suasor/slack-triage"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/slack-triage/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.

agentmods 80×15 button for slack-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/ozzy-labs/suasor/slack-triage"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/slack-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 168 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,763 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00168 $0.01763
Opus 5 $0.00084 $0.00881
Sonnet 5 $0.00034 $0.00353
Haiku 4.5 $0.00017 $0.00176

Measured 11d ago against content hash 7a6b0730abf4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

slack-triage 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.

docs/skills/slack-triage/SKILL.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

slack-triage

Slack の @mention / DM を「読むべきが未処理」signal として集約し、捌く HITL write skill（ADR-0012 / ADR-0013 / ADR-0041）。demand の列挙は read で自律 OK だが、action 化（task / decision / 返信 / inbox 捕捉）や seen 印付け（demand.mark（state））で write tool を HITL で呼ぶため boundary は write（auto-apply なし・ADR-0004）。next-actions / brief が priority.list 経由で取り込む demand を、Slack 起点で正面から扱う。

いつ発火するか

  • 「Slack の未処理を捌いて」「Slack の未読対応」
  • 「mention/DM まとめて」「Slack で呼ばれてるやつ」「@ 付き拾って」

何をするか（MCP tool flow）

read で集めて、action 化（write）は HITL（ADR-0004）。

  1. demand.list（source="slack"）で未処理 signal を集める。kinds（mention / dm）/ selfUserId（mention 用、未指定時は config の self_user_id）/ observedAfter / observedBefore で絞る。取り込み済み slack_message source からの query 導出で、専用 projection は持たない（ADR-0012 / ADR-0041）。既定は un-acked のみ（demand.mark（state） 済みは除外）。各 demand は source の externalId / body / observedAt + source + kind + channelName / userName（ローカル projection から join した人間可読名。sync が名前解決していれば埋まり、未解決なら null＝meta の生 id に fallback。ADR-0037 §3/§10。live fetch なし）
  2. demand を kind（mention / dm）・新しさで整理し、ユーザーに提示する（ここまで read で自律 OK）。提示は 生 id（C… / U…）ではなく名前を使う: 「#<channelName> で <userName> にメンションされています」のように channelName / userName を用い、null（未解決）のときだけ meta.channel / meta.user の id に fallback する。名前が全面 id-only のままなら slack resolve-names で既取り込み分を遡及解決できる（ADR-0037 §11）
  3. action が要るものは HITL で橋渡しする（人の承認後のみ）:
    • 受信箱に捕捉 — inbox.add（sourceExternalId）で open 捕捉し、以後 inbox-triage で解決する
    • task / decision / 返信下書き化 — source.get で本文を読み、propose.generate（mode=source_extract）で候補を生成 → propose.list で確認 → 承認分のみ propose.apply（source-extract と同じ flow）
    • 返信したいだけ — reply-draft skill（propose.generate mode=reply_draft、reply_to_source_id 指定）へ
  4. 処理した demand は demand.mark（state="acked"）（対応した）、対応不要なものは demand.mark（state="dismissed"）（外す）で印を付ける（HITL）。以後 既定の demand.list / priority.list / brief から外れる（ADR-0041）。task 化 / inbox 捕捉した mention はそのまま ack して二重計上を防ぐ

Read the full file on GitHub · 53 lines

Changes

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.

  1. 11d ago First seen · 53 lines · 168 tokens per session scan A 7a6b0730abf4

Subscribe to this mod's changes

slack-triage is a skill published in the GitHub repository ozzy-labs/suasor (0 stars, last pushed 1mo ago), licensed MIT. It adds 168 tokens to every session and 1,763 once invoked, about $0.0008 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.

Project managementtriage
Related

Other skills, from other repositories

issue-triage

Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).

paperclipai/paperclip · 48 tokens

Jira QA Workflows

Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.

PramodDutta/qaskills · 45 tokens

gitlab-issues

Issue review and tracking on GitLab via the gitlab-api MCP server — review a project's issues, review issues across a whole group/organization, and read, create, update, or close an issue with the domain-typed tool. Use when the agent must triage a project's issues, see every issue affecting a group, open a new issue…

Knuckles-Team/gitlab-api · 128 tokens

DSAR Workflow

Use when an organization receives a data subject access request (or any data subject rights request) and needs a structured triage, handling record, and response plan for attorney review.

zgbrenner/agentcounsel · 39 tokens

Legal Intake Triage

Use when an inbound business request reaches the legal team — an email, ticket, form submission, or chat ask — to produce a structured intake triage that classifies the request, captures urgency as stated, surfaces conflict-check and confidentiality questions, and proposes a routing recommendation for the legal team…

zgbrenner/agentcounsel · 65 tokens

mk:decision-framework

Operational decision frameworks: triage, escalation, case management, billing ops. Use for 'how to handle X cases', 'build triage', 'escalation protocol'.

ngocsangyem/MeowKit · 40 tokens