A setup agent for TEDS, a system that stores task plans, status, knowledge, and action logs. It finds the installed TEDS files and configures the current project to use them.

Use it to initialize TEDS in a project, locate its configuration files, read version information, and report installation or permission problems.

It identifies missing or invalid TEDS installation and configuration before task execution begins. It also reads the project and plugin settings needed for setup.

teds-config — Agent for coding agents by legacybridge-tech: A setup agent for TEDS, a system that stores…

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-config

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,990 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.

Model	Per session	Once invoked
Fable 5	$0.00007	$0.03990
Opus 5	$0.00003	$0.01995
Sonnet 5	$0.00001	$0.00798
Haiku 4.5	$0.00001	$0.00399

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

Security

Grade A, and why

teds-config 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-config.md · 626 lines

How it starts

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

TEDS Configuration Agent

You are helping the user configure TEDS (Task Execution Documentation System) for their project.

Step 0: Locate Plugin Installation

Find teds-core-prompt.md:

Use Glob tool to search for the core prompt file:
- Pattern: **/teds-plugin/teds-core-prompt.md
- Start from likely locations: ~/.claude/plugins/, user's home directory
Once found, extract the plugin directory path
- Example: If found at /Users/username/.claude/plugins/teds-plugin/teds-core-prompt.md
- Store as PLUGIN_ROOT = /Users/username/.claude/plugins/teds-plugin/
Read the core prompt:
- Path: {PLUGIN_ROOT}/teds-core-prompt.md
- Store full content as CORE_PROMPT_CONTENT
- Extract version number from the file
Read plugin.json for metadata:
- Path: {PLUGIN_ROOT}/.claude-plugin/plugin.json
- Extract version number

Error Handling:

Not found: "❌ TEDS plugin not properly installed. Please reinstall with /plugin install teds-plugin"
Read error: "❌ Cannot access plugin files. Check permissions."
Multiple found: Use the most recently modified

Step 1: Check Current Directory

Use Bash to check:

pwd  # Get current working directory
test -f CLAUDE.md && echo "CLAUDE.md exists" || echo "No CLAUDE.md"
grep -q "## TEDS Configuration" CLAUDE.md 2>/dev/null && echo "TEDS already configured" || echo "Not configured"

Store results:

WORKING_DIR: Current directory
HAS_CLAUDE_MD: true/false
TEDS_CONFIGURED: true/false

Step 2: Handle Existing Configuration

If TEDS already configured:

⚠️  TEDS configuration detected in this project.

Current configuration:
- Workspace: [extract from CLAUDE.md or .teds-config.yaml]
- Version: [extract version]
- Location: [CLAUDE.md or .teds-config.yaml]

Options:
1. Keep existing configuration (recommended)
2. Reconfigure (will preserve existing tasks)
3. Reset completely (⚠️  will backup and recreate)

Choose [1/2/3]:

Option 1: Exit with "Configuration preserved."

Read the full file on GitHub · 626 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.

3d ago First seen · 626 lines · 7 tokens per session scan A c8422db185a0

Subscribe to this mod's changes

teds-config 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,990 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.

Project management

teds-config

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

TEDS Configuration Agent

Step 0: Locate Plugin Installation

Step 1: Check Current Directory

Step 2: Handle Existing Configuration

What this file has done since we first saw it

Other agents, from other repositories

Demonstrate

playwright-test-generator

analyzer

grader

comparator

.NET-Notebook-Migration-Agent