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 jeremylongworth-source/AgentSkills --skill community-triagegit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/community-triage)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/community-triage"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/community-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.
<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/community-triage"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/community-triage.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.00078 | $0.00528 |
| Opus 5.5 | $0.00031 | $0.00211 |
| Sonnet 5.5 | $0.00016 | $0.00106 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
community-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 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Triage
Core Workflow
- Identify the source, audience context, message text, public/private status, platform, thread context, requested action, and available policy or brand guidance.
- Classify each item by intent, urgency, sentiment, risk, owner, and next action.
- Separate audience-facing reply candidates from internal notes, moderation questions, escalation needs, and missing context.
- Flag items that need human review before response, removal, escalation, sponsor visibility, refund/account support, legal/compliance review, or crisis handling.
- Draft a triage table and summary. Use
reply-draftingonly for reviewed response drafts after triage is clear. - Keep all community, social, CRM, support, moderation, publishing, and member systems read-only unless the user approves a specific action.
Classification Fields
- Channel or source
- Message summary
- Intent
- Sentiment
- Urgency
- Risk level
- Suggested owner
- Next action
- Public reply candidate
- Private/internal note
- Missing context
- Escalation reason
Safety Rules
- Do not send replies, delete comments, ban users, mute users, approve members, change roles, publish posts, or update community tools without explicit approval.
- Do not invent audience quotes, identity, sentiment, member status, threats, screenshots, policy violations, metrics, or relationship history.
- Escalate harassment, threats, self-harm, minors, doxxing, hate, legal claims, privacy issues, payment/account issues, sponsor conflicts, and crisis or reputation risks.
- Verify current platform policy only when giving platform-specific tactical guidance.
Deliverable Shape
For community triage, provide:
- Triage summary
- Message table
- Priority queue
- Draft reply candidates
- Escalation list
- Missing context
- Review owner
- Approval status
References
- Read
references/community-triage-checklist.mdwhen preparing a creator community triage table or priority queue.
What ships with it
2 files 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 First seen · 71 lines · 78 tokens per session scan A 956debd840a1
community-triage is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 78 tokens to every session and 528 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
idd-spec-audit
Semantic audit of the IDD instruction corpus for leaked session context, cross-file contradictions, fresh-memory completability gaps, automation blockers, and restatement-discipline drift. Use on request to audit .github/instructions, the issue-authoring skill bundle, and the installed agent entry files (CLAUDE.md…
unity-yaml-format
Inspect, explain, diff, and carefully edit Unity text-serialized files such as .unity, .prefab, .asset, and related YAML-based project files. Use when mapping class IDs and fileIDs, tracing object references, reviewing merge conflicts, or making minimal safe edits to existing UnityYAML documents.
authos-rbac-control
Manage AuthOS organization members, roles, invitations, SCIM tokens, and capability-based permissions. Use when implementing team administration, custom roles, service access grants, invitation flows, SCIM provisioning, or authorization checks inside an AuthOS tenant.
authos-service-management
Manage AuthOS tenant services, OAuth client credentials, redirect URIs, device activation URIs, plans, API keys, SAML settings, and checkout. Use when creating or configuring applications inside an AuthOS organization.
authos-platform-deployment
Deploy and configure an AuthOS API instance from source or Docker. Use when setting database backend, JWT signing keys, environment variables, billing provider, SMTP, GeoIP, Docker images, health checks, or production reverse proxy settings.
tester
Run end-to-end web quality audits with Playwright and Lighthouse using existing project scripts first. Use when the user says /tester, e2e test, smoke test, Playwright audit, Lighthouse audit, performance audit, accessibility audit, dark mode audit, mobile audit, or asks for 100/100 Lighthouse improvement guidance.