triaging-overdue-work

triaging-overdue-work is a skill for Claude Code from AstravueOrg/astravue-mcp-server. It costs 73 tokens per session (524 once invoked), scanned A, original, Apache-2.0.

A process for reviewing late or endangered work in Astravue, a task-management system, before deciding what should happen to it.

In plain words
What is it for?
Use it to inspect overdue tasks, check blockers and workload, and propose rescheduling, reassignment, deprioritisation, or closure.
Why use it?
It helps explain why work is late and prevents tasks from being changed without the user's approval.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the astravue plugin — 8 skills, 2 MCP servers shipped together

Good fit Use it to inspect overdue tasks, check blockers and workload, and propose rescheduling, reassignment, deprioritisation, or closure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/astravueorg/astravue-mcp-server/triaging-overdue-work
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 AstravueOrg/astravue-mcp-server --skill triaging-overdue-work
Clone the repo
git clone --depth 1 https://github.com/AstravueOrg/astravue-mcp-server

Made for: Claude Code.

Or install astravue, the plugin that ships this one along with the rest of its 8 skills, 2 MCP servers.

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 triaging-overdue-work

README.md
[![agentmods](https://agentmods.dev/badge/skills/astravueorg/astravue-mcp-server/triaging-overdue-work/github.svg)](https://agentmods.dev/skills/astravueorg/astravue-mcp-server/triaging-overdue-work)
Your own site
<a href="https://agentmods.dev/skills/astravueorg/astravue-mcp-server/triaging-overdue-work"><img src="https://agentmods.dev/badge/skills/astravueorg/astravue-mcp-server/triaging-overdue-work/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 triaging-overdue-work

Your own site · 80×15
<a href="https://agentmods.dev/skills/astravueorg/astravue-mcp-server/triaging-overdue-work"><img src="https://agentmods.dev/badge/skills/astravueorg/astravue-mcp-server/triaging-overdue-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 524 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.00073 $0.00524
Opus 5 $0.00036 $0.00262
Sonnet 5 $0.00015 $0.00105
Haiku 4.5 $0.00007 $0.00052

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

Security

Grade A, and why

triaging-overdue-work 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.

skills/triaging-overdue-work/SKILL.md · 46 lines

What it actually says

Triaging Overdue Work

Read first, decide, then act. The goal is to turn a pile of late tasks into a short list of concrete decisions the user signs off on — not to silently mutate the board.

Workflow

  1. Pull the overdue picture

    • astravue_list_overdue_tasks — the late tasks with how far past due
    • astravue_get_task_counts — overall status distribution for context

    Confirm the project scope first if it isn't clear (astravue_list_projects).

  2. Assess each overdue task

    For each, work out why it's late and what should happen:

    • Is it blocked? Check astravue_list_dependencies — a blocked task can't just be rescheduled; the blocker must move first.
    • Is it still relevant? Stale tasks may be closeable.
    • Is the owner overloaded? Group by assignee to spot pile-ups.
    • Is it genuinely just late? Then it needs a realistic new due date.

    Categorize each into: reschedule, reassign, deprioritize, or close.

  3. Propose a triage plan and confirm

    Present the tasks grouped by recommended action, each with a one-line reason. Ask the user to approve, adjust, or drop items. Do not change any task before approval — rescheduling and reassigning are visible to the whole team.

  4. Apply after approval

    • astravue_bulk_update_tasks — apply due-date, status, priority, or assignee changes in one pass
    • astravue_mark_notification_read / notification tools — only if the user wants to clear related noise

    Report what changed, and note any blocked tasks that still need their blocker resolved.

Important

  • Read and propose before mutating — these changes are team-visible.
  • A blocked task's blocker must move first; don't just push the blocked task's date.
  • Don't auto-close stale tasks — surface them and let the user decide.
  • Give every proposed action a concrete reason, not just "overdue".
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 · 46 lines · 73 tokens per session scan A c625b59e6f67

Subscribe to this mod's changes

triaging-overdue-work is a skill published in the GitHub repository AstravueOrg/astravue-mcp-server (12 stars, last pushed 16d ago), licensed Apache-2.0. It adds 73 tokens to every session and 524 once invoked, about $0.0004 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-30.