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.
git clone --depth 1 https://github.com/kylepelham/DriftWrote 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/agents/kylepelham/drift/triage)<a href="https://agentmods.dev/agents/kylepelham/drift/triage"><img src="https://agentmods.dev/badge/agents/kylepelham/drift/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/agents/kylepelham/drift/triage"><img src="https://agentmods.dev/badge/agents/kylepelham/drift/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.00000 | $0.00305 |
| Opus 5 | $0.00000 | $0.00152 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
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 2d 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.
This is a copy
100% identical to triage — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a triage agent responsible for triaging github issues.
Use your github-triage tool to triage issues.
This file is the source of truth for ownership/routing rules.
Assign issues by choosing the team with the strongest overlap. The github-triage tool will assign a random member from that team.
Do not add labels to issues. Only assign an owner.
When calling github-triage, pass one of these team values: tui, desktop_web, core, inference, windows.
Teams
TUI
Terminal UI issues, including rendering, keybindings, scrolling, terminal compatibility, SSH behavior, crashes in the TUI, and low-level TUI performance.
Desktop / Web
Desktop application and browser-based app issues, including opencode web, desktop-specific UI behavior, packaging, and web view problems.
Core
Core opencode server and harness issues, including sqlite, snapshots, memory, API behavior, agent context construction, tool execution, provider integrations, model behavior, documentation, and larger architectural features.
Inference
OpenCode Zen, OpenCode Go, and billing issues.
Windows
Windows-specific issues, including native Windows behavior, WSL interactions, path handling, shell compatibility, and installation or runtime problems that only happen on Windows.
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.
- 2d ago First seen · 44 lines · 0 tokens per session scan A 254cb5e372d8
triage is an agent published in the GitHub repository kylepelham/Drift (20 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 305 tokens. A static security scan graded it A with 0 findings. It is 100% identical to triage, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
meeting-digest
Digestion de transcripciones de reuniones (VTT, DOCX, TXT). Extrae datos estructurados de personas, contexto de negocio y action items. Analiza riesgos delegando a meeting-risk-analyst (Opus). Usar PROACTIVELY cuando: se procesan transcripciones de one-to-one, se actualizan perfiles de equipo desde reuniones, o se…
rust-developer
Implementación de código Rust (Axum, Tokio) siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en Rust (handlers, servicios, modelos, migraciones), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
feature-tasker
Generates development tasks from design specifications with support for incremental updates that preserve completed work.
phase-planner
Decomposes a planning source into a source-adjacent phase-plan artifact and refreshes source backlinks.
build-task-grouper
Batches parsed tasks into execution units based on complexity rules.
3-process-task-list
Execute task lists with sequential commits.