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-statusgit clone --depth 1 https://github.com/legacybridge-tech/claude-pluginsWrote 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.
[](https://agentmods.dev/commands/legacybridge-tech/claude-plugins/teds-status)<a href="https://agentmods.dev/commands/legacybridge-tech/claude-plugins/teds-status"><img src="https://agentmods.dev/badge/commands/legacybridge-tech/claude-plugins/teds-status.svg" alt="Measured on agentmods" height="20"></a>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.00006 | $0.01008 |
| Opus 5 | $0.00003 | $0.00504 |
| Sonnet 5 | $0.00001 | $0.00202 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade A, and why
teds-status 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
View TEDS Task Status
Launch the teds-status agent to display comprehensive status of your TEDS tasks.
Usage
# View all tasks
/teds-status
# View specific task details
/teds-status task-id
Examples
# List all active tasks
/teds-status
# Detailed status for one task
/teds-status 20250116-1430-refactor-auth
All Tasks View
When called without arguments, shows summary of all tasks:
# TEDS Tasks Status
## Active Tasks (2)
ID | Name | Phase | Progress | Status
----------------------------|-------------------|----------------|----------|--------
20250116-1430-refactor-auth | refactor-auth | Implementation | 45% | active
20250115-0920-migrate-db | migrate-database | Testing | 78% | active
## Recently Completed (1)
ID | Name | Completed | Duration
----------------------------|-------------------|-----------------|----------
20250114-1100-update-deps | update-deps | 2 hours ago | 3.5 hours
Run `/teds-status [task-id]` for detailed information.
Single Task View
When called with a task ID, shows detailed status:
# Task Status: refactor-auth
**ID**: 20250116-1430-refactor-auth
**Status**: Active (not blocked)
**Phase**: Phase 2 - Implementation
**Progress**: 45%
**Created**: 2025-01-16 14:30
**Last Updated**: 2 minutes ago
**Last Checkpoint**: 45 minutes ago
## Next Action
Implement OAuth flow integration with Google provider
## Recent Activity (Last 5 actions)
### 16:45 - File Edit
- Tool: Edit
- Target: src/auth/AuthService.ts
- Result: Added OAuth configuration interface
- Status: success
### 16:42 - File Creation
- Tool: Write
- Target: src/auth/OAuthProvider.ts
- Result: Created OAuth provider abstract class
- Status: success
### 16:38 - Read Documentation
- Tool: Read
- Target: docs/oauth-spec.md
- Result: Reviewed OAuth 2.0 specification
- Status: success
[... 2 more recent actions ...]
## Key Learnings
- Google OAuth requires web credentials, not service account
- Need to handle refresh token expiration gracefully
- PKCE extension recommended for enhanced security
## Issues
None - task is progressing normally
---
Continue: `/teds-continue 20250116-1430-refactor-auth`
Checkpoint: `/teds-checkpoint 20250116-1430-refactor-auth`
Complete: `/teds-complete 20250116-1430-refactor-auth`
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.
- 4d ago First seen · 169 lines · 6 tokens per session scan A 2bb0e1a9d003
teds-status is a command published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 6 tokens to every session and 1,008 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
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.