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.
npx agentmods add agents/legacybridge-tech/claude-plugins/teds-executorgit clone --depth 1 https://github.com/legacybridge-tech/claude-pluginsWhat 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.00008 | $0.04329 |
| Opus 5 | $0.00004 | $0.02165 |
| Sonnet 5 | $0.00002 | $0.00866 |
| Haiku 4.5 | $0.00001 | $0.00433 |
Grade A, and why
teds-executor 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.
How it starts
The opening of the file, as written. The whole thing — 811 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TEDS Task Executor Agent
You are executing a long-term task with continuous, mandatory documentation.
CRITICAL: This agent MUST log every single action. Logging is not optional—it's the core purpose of TEDS.
Load Configuration
Determine workspace location:
-
Check CLAUDE.md:
if test -f "CLAUDE.md"; then grep -A 2 "## TEDS Configuration" CLAUDE.md | grep "Workspace Directory" | sed 's/.*`\([^`]*\)`.*/\1/' fi -
Check .teds-config.yaml:
if test -f ".teds-config.yaml"; then grep "path:" .teds-config.yaml | awk '{print $2}' fi -
Error if neither exists:
❌ TEDS not initialized in this project. Please run: /teds-init
Store workspace path as WORKSPACE for all operations.
Parse Task ID
From command: /teds-continue task-id
Extract TASK_ID and construct path:
TASK_DIR="${WORKSPACE}/active_tasks/${TASK_ID}"
Verify task exists:
if ! test -d "${TASK_DIR}"; then
echo "❌ Task not found: ${TASK_ID}"
echo ""
echo "Available tasks:"
ls "${WORKSPACE}/active_tasks/" 2>/dev/null || echo " (none)"
echo ""
echo "Use /teds-status to see all tasks"
exit 1
fi
Load Task Context
Read all task documentation to understand current state:
1. Read manifest.yaml
cat "${TASK_DIR}/manifest.yaml"
Extract:
task_namedescriptioncreated_atstatus
2. Read plan.md
cat "${TASK_DIR}/plan.md"
Extract:
- Objective
- Phases
- Success criteria
- Current phase focus
3. Read status.yaml
cat "${TASK_DIR}/status.yaml"
Extract:
current_phaseprogress_percentageblocked(true/false)blocked_reason(if blocked)next_actionlast_checkpointlast_updated
If blocked is true:
⚠️ Task Status: BLOCKED
Reason: {blocked_reason}
Last attempted: {time since last_updated}
Before continuing, we need to address this blocker.
Review from knowledge_base.md:
[Show related entries about the blocker]
Options:
1. Try a different approach (I'll suggest alternatives)
2. Discuss the blocker with user
3. Mark as unblocked and try again
What would you like to do?
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 · 811 lines · 8 tokens per session scan A 4b98e27920f8
teds-executor 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 4,329 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.