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 commands/legacybridge-tech/claude-plugins/teds-continuegit 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.00591 |
| Opus 5 | $0.00004 | $0.00296 |
| Sonnet 5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
teds-continue 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continue TEDS Task
Launch the teds-executor agent to resume work on an existing long-term task.
Usage
/teds-continue task-id
Examples
# Continue specific task
/teds-continue 20250116-1430-refactor-auth
# List available tasks first
/teds-status
# Then continue one
/teds-continue 20250116-1430-migrate-database
What This Does
The executor agent will:
- Load TEDS configuration
- Read all task documentation:
manifest.yaml- Task infoplan.md- Execution planexecution_log.md- Recent actions (last 20 entries)knowledge_base.md- Accumulated learningsstatus.yaml- Current state
- Identify last completed action
- Check for any blocked status
- Resume from
next_actionin status.yaml - Continue with mandatory logging after every action
Task Recovery
If you're resuming after a break, the agent will:
- Show you what was accomplished previously
- Identify where work stopped
- Confirm the next action before proceeding
- Catch you up on any important context
Example output:
📋 Resuming Task: refactor-auth (20250116-1430-refactor-auth)
Last session: 2 hours ago
Progress: 45% (Phase 2: Implementation)
Last action: Created new AuthService class
Status: Active (not blocked)
Next: Implement OAuth flow integration
Continue with next action? [y/n]
Mandatory Logging
While working, the executor agent will:
- Log EVERY action to
execution_log.md - Update
status.yamlon state changes - Add discoveries to
knowledge_base.md - Create checkpoints every 30+ minutes
You don't need to remind the agent to log—it's built into the system.
Checkpoints
The agent automatically creates checkpoints:
- Every 30+ minutes of work
- At major milestones
- When you request:
/teds-checkpoint
Checkpoints are safe pause points where you can stop and resume later.
If Task is Blocked
If the status shows blocked: true, the agent will:
- Explain what caused the block
- Review attempted solutions
- Propose new approaches or ask for guidance
- Update status once unblocked
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 · 97 lines · 8 tokens per session scan A fdf9e0d9a841
teds-continue is a command 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 591 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).