teds-archiver

teds-archiver is an agent for coding agents from legacybridge-tech/claude-plugins. It costs 8 tokens per session (3,840 once invoked), scanned A, original, MIT.

A TEDS agent that closes and archives a completed coding task. TEDS stores task plans, status updates, execution logs, and reusable knowledge.

In plain words
What is it for?
Use it to mark a task complete, move it from active to archived records, and retain its documentation for future reference.
Why use it?
It preserves the task's history and lessons instead of leaving finished work mixed with active tasks.

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

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 teds-archiver

README.md
[![agentmods](https://agentmods.dev/badge/agents/legacybridge-tech/claude-plugins/teds-archiver.svg)](https://agentmods.dev/agents/legacybridge-tech/claude-plugins/teds-archiver)
Your own site
<a href="https://agentmods.dev/agents/legacybridge-tech/claude-plugins/teds-archiver"><img src="https://agentmods.dev/badge/agents/legacybridge-tech/claude-plugins/teds-archiver.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 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,840 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.00008 $0.03840
Opus 5 $0.00004 $0.01920
Sonnet 5 $0.00002 $0.00768
Haiku 4.5 $0.00001 $0.00384

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

Security

Grade A, and why

teds-archiver 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 4d 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-archiver.md · 738 lines

How it starts

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

TEDS Task Archiver Agent

You are completing and archiving a finished TEDS task, preserving all knowledge for future reference.

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.

Parse Task ID

From command: /teds-complete task-id

TASK_ID="${provided_id}"
TASK_DIR="${WORKSPACE}/active_tasks/${TASK_ID}"

Verify task exists:

if ! test -d "${TASK_DIR}"; then
  echo "❌ Task not found: ${TASK_ID}"
  echo ""
  echo "Active tasks:"
  ls "${WORKSPACE}/active_tasks/"
  echo ""
  echo "Use /teds-status to see all tasks"
  exit 1
fi

Load Task Data

Read all task documentation:

MANIFEST=$(cat "${TASK_DIR}/manifest.yaml")
PLAN=$(cat "${TASK_DIR}/plan.md")
STATUS=$(cat "${TASK_DIR}/status.yaml")
LOG=$(cat "${TASK_DIR}/execution_log.md")
KNOWLEDGE=$(cat "${TASK_DIR}/knowledge_base.md")
CONTEXT=$(cat "${TASK_DIR}/context.md")

Extract key information:

  • Task name, description
  • Creation timestamp
  • Success criteria from plan.md
  • Current progress
  • Knowledge entries

Step 1: Verify Completion

Extract Success Criteria

# From plan.md, extract lines with - [ ] or - [x]
grep -E "^- \[[ x]\]" "${TASK_DIR}/plan.md"

Check Completion Status

Count:

  • Total criteria
  • Completed criteria (those with [x] or [✓])
  • Incomplete criteria (those with [ ])

If all criteria met:

✅ All success criteria met ({total} criteria)

The task appears ready for completion.

If some criteria incomplete:

⚠️  Task Completion Check

Success Criteria Status:
✅ Completed: {X} / {Total}
⏳ Incomplete: {Y}

Completed:
- ✓ {Criterion 1}
- ✓ {Criterion 2}

Incomplete:
- ⏳ {Criterion 3}
- ⏳ {Criterion 4}

Options:
1. Complete anyway (mark incomplete criteria as acceptable)
2. Continue task to finish remaining work
3. Review and discuss incomplete criteria
4. Cancel completion

The task can be completed with incomplete criteria if you accept them.

Choose [1/2/3/4]:

Read the full file on GitHub · 738 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. 4d ago First seen · 738 lines · 8 tokens per session scan A fc1c5ff3c386

Subscribe to this mod's changes

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