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/ggprompts/tfe/readmegit clone --depth 1 https://github.com/GGPrompts/TFEWrote 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/ggprompts/tfe/readme)<a href="https://agentmods.dev/commands/ggprompts/tfe/readme"><img src="https://agentmods.dev/badge/commands/ggprompts/tfe/readme.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.00000 | $0.02986 |
| Opus 5 | $0.00000 | $0.01493 |
| Sonnet 5 | $0.00000 | $0.00597 |
| Haiku 4.5 | $0.00000 | $0.00299 |
Grade A, and why
README 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 — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TFE Development Slash Commands
These slash commands leverage Desktop Commander MCP to provide powerful development workflows for TFE.
📋 Available Commands
Legend:
- 🎯 Core commands - Use these most often
- ⭐ Advanced features - Powerful when you need them
/tail-logs - Monitor TFE Runtime
Purpose: Continuously monitor TFE for errors, panics, and issues during development.
What it does:
- Checks if TFE is running (tmux or background process)
- Monitors process output in real-time
- Supports tmux monitoring - can watch your interactive TFE session!
- Alerts you to errors, panics, stack traces
- Automatically reads and analyzes problematic code
- Suggests fixes proactively
When to use:
- While developing new features
- When debugging issues
- During manual testing sessions
- Anytime you want real-time error detection
Example (tmux mode):
You: /tail-logs
Claude: Are you running TFE in a tmux session?
You: Yes, session name is "tfe-dev"
Claude: ✅ Monitoring tmux session 'tfe-dev'
📍 TFE browsing: /home/matt/projects/TFE
👁️ Previewing: README.md
No errors detected
[You navigate in TFE...]
Claude: 📄 I see you opened types.go. The model struct
is getting large - want suggestions for refactoring?
Example (background mode):
You: /tail-logs
Claude: Are you running TFE in a tmux session?
You: No
Claude: ✅ Started TFE in background (PID 12345)
Monitoring output...
[You work on code...]
Claude: ⚠️ Panic detected in file_operations.go:234!
Nil pointer dereference in loadFiles()
Here's the issue and a suggested fix...
/watch-tmux - Advanced Tmux Monitoring ⭐ NEW
Purpose: Dedicated tmux session monitoring with full TUI visibility.
What it does:
- Captures and parses tmux pane output
- Sees the actual Bubbletea TUI - not just logs!
- Detects what directory you're browsing
- Knows what file you're previewing
- Monitors for crashes, errors, panics
- Can see visual rendering issues
- Provides context-aware suggestions
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 · 493 lines · 0 tokens per session scan A e92fff9bb95b
README is a command published in the GitHub repository GGPrompts/TFE (20 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,986 tokens. 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-30.
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.