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-startgit 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.00009 | $0.00540 |
| Opus 5 | $0.00005 | $0.00270 |
| Sonnet 5 | $0.00002 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
teds-start 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start New TEDS Task
Launch the teds-initializer agent to create and initialize a new long-term task.
Usage
/teds-start task-name [optional-description]
Examples
# Simple task
/teds-start refactor-auth
# With description
/teds-start migrate-database "Migrate from MySQL to PostgreSQL"
# Complex project
/teds-start implement-oauth "Implement OAuth 2.0 authentication system with Google and GitHub providers"
What This Does
The agent will:
- Load TEDS configuration (from CLAUDE.md or .teds-config.yaml)
- Generate a unique task ID (format:
YYYYMMDD-HHMM-taskname) - Create complete directory structure for the task
- Initialize all documentation files:
manifest.yaml- Task metadataplan.md- Execution plan (will work with you to define)execution_log.md- Action loggingknowledge_base.md- Learnings repositorycontext.md- Background and constraintsstatus.yaml- Current state
- Set initial status to "active"
- Begin planning with you
Task Naming Guidelines
Good task names:
refactor-auth- Clear and concisemigrate-database- Specific actionimplement-oauth- Feature-focused
Avoid:
task1- Too genericfix-bug- Not specific enoughupdate-everything- Too broad
After Initialization
Once the task is initialized, you'll see:
✅ Task initialized: 20250116-1430-refactor-auth
Location: claude_work_space/active_tasks/20250116-1430-refactor-auth/
Status: Ready to begin
The agent will then help you:
- Define detailed phases in
plan.md - Set success criteria
- Document context and constraints
- Begin execution with continuous logging
Continuing Later
To resume this task in a future session:
/teds-continue 20250116-1430-refactor-auth
Related Commands
/teds-status- View all tasks/teds-continue [task-id]- Resume a task/teds-checkpoint- Save progress/teds-complete [task-id]- Finish and archive
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 · 84 lines · 9 tokens per session scan A 0d797735ab0a
teds-start is a command published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 540 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.