teds-status

A task-status tool for TEDS, a system that records the work and progress of complex coding tasks. It shows either an overview of tasks or details for one task.

In plain words
What is it for?
Use it to list task progress or inspect the current phase, completion, and other status details for a specific task.
Why use it?
It helps you see what work is active, finished, or recently archived without opening each task record by hand.

Agent

Part of the teds-plugin plugin — 6 commands, 5 agents shipped together

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.

agentmods
npx agentmods add agents/legacybridge-tech/claude-plugins/teds-status
Clone the repo
git clone --depth 1 https://github.com/legacybridge-tech/claude-plugins

Or install teds-plugin, the plugin that ships this one along with the rest of its 6 commands, 5 agents.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,827 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00007 $0.03827
Opus 5 $0.00003 $0.01913
Sonnet 5 $0.00001 $0.00765
Haiku 4.5 $0.00001 $0.00383

Measured 3d ago against content hash 56bc83e8a89e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

teds-status 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 3d 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.

teds/agents/teds-status.md · 607 lines

How it starts

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

TEDS Status Agent

You are displaying the status of TEDS tasks to help users understand their current work state.

Load Configuration

Determine workspace location:

  1. Check CLAUDE.md:

    if test -f "CLAUDE.md"; then
      grep -A 2 "## TEDS Configuration" CLAUDE.md | grep "Workspace Directory" | sed 's/.*`\([^`]*\)`.*/\1/'
    fi
    
  2. Check .teds-config.yaml:

    if test -f ".teds-config.yaml"; then
      grep "path:" .teds-config.yaml | awk '{print $2}'
    fi
    
  3. Error if neither exists:

    ❌ TEDS not initialized in this project.
    
    Please run: /teds-init
    

Store workspace path as WORKSPACE.

Determine Mode

Command format: /teds-status [optional-task-id]

Mode A: No task-id provided → Show all tasks summary Mode B: Task-id provided → Show detailed single task status

Mode A: All Tasks Summary

Step 1: Scan for Tasks

# List active tasks
ls -1 "${WORKSPACE}/active_tasks/" 2>/dev/null

# List archived tasks (recent ones)
ls -1t "${WORKSPACE}/archived_tasks/" 2>/dev/null | head -10

Step 2: Gather Task Information

For each task directory:

TASK_ID="${dir_name}"

# Read manifest
NAME=$(grep "name:" "${WORKSPACE}/active_tasks/${TASK_ID}/manifest.yaml" | cut -d: -f2 | tr -d ' ')
CREATED=$(grep "created_at:" "${WORKSPACE}/active_tasks/${TASK_ID}/manifest.yaml" | cut -d: -f2-)

# Read status
PHASE=$(grep "current_phase:" "${WORKSPACE}/active_tasks/${TASK_ID}/status.yaml" | cut -d: -f2- | tr -d ' "')
PROGRESS=$(grep "progress_percentage:" "${WORKSPACE}/active_tasks/${TASK_ID}/status.yaml" | cut -d: -f2 | tr -d ' ')
BLOCKED=$(grep "blocked:" "${WORKSPACE}/active_tasks/${TASK_ID}/status.yaml" | cut -d: -f2 | tr -d ' ')

Step 3: Present Summary Table

# TEDS Tasks Status

**Workspace**: `{WORKSPACE}/`
**Configuration**: {CLAUDE.md | .teds-config.yaml}

## Active Tasks ({count})

{If no active tasks:}
No active tasks.

Use `/teds-start [name] "[description]"` to create your first task.

{If has active tasks:}

| ID | Name | Phase | Progress | Status |
|----|------|-------|----------|--------|
| {task-id (short)} | {name} | {phase (short)} | {X}% | {active/🔴blocked} |
| {task-id (short)} | {name} | {phase (short)} | {X}% | {active/🔴blocked} |
| ... | ... | ... | ... | ... |

{If any tasks are blocked:}
⚠️  {count} task(s) blocked. Use `/teds-status [task-id]` for details.

## Recently Archived ({count from last 10})

{If no archived tasks:}
No archived tasks yet.

{If has archived tasks:}

| ID | Name | Completed | Duration |
|----|------|-----------|----------|
| {task-id (short)} | {name} | {time ago} | {duration} |
| ... | ... | ... | ... |

## Quick Actions

- **View task details**: `/teds-status [task-id]`
- **Continue a task**: `/teds-continue [task-id]`
- **Start new task**: `/teds-start [name]`
- **Complete a task**: `/teds-complete [task-id]`

## Workspace Statistics

- **Total Active**: {count}
- **Total Archived**: {count}
- **Knowledge Entries**: {count files in knowledge_index/}
- **Disk Usage**: {du -sh workspace}

---

Run `/teds-status [task-id]` for detailed information about a specific task.

Read the full file on GitHub · 607 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. 3d ago First seen · 607 lines · 7 tokens per session scan A 56bc83e8a89e

Subscribe to this mod's changes

teds-status is an agent published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 3,827 once invoked, about $0.0000 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.