Borrowing it
Nothing to install: this file belongs to GGPrompts/TFE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GGPrompts/TFE/main/.claude/commands/test-tfe-feature.mdgit 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/test-tfe-feature)<a href="https://agentmods.dev/commands/ggprompts/tfe/test-tfe-feature"><img src="https://agentmods.dev/badge/commands/ggprompts/tfe/test-tfe-feature.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.1 | $0.00009 | $0.00633 |
| Opus 5 | $0.00005 | $0.00316 |
| Sonnet 5 | $0.00002 | $0.00127 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
test-tfe-feature 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 6d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test TFE Feature
You are helping test a specific feature in TFE by monitoring the application during manual testing.
Your Task
Use bash and tmux to safely monitor TFE while the user manually tests a feature.
-
Prepare for testing
- Rebuild TFE if needed (ask me first)
- Launch TFE in a detached tmux session (not via start_process to avoid terminal corruption)
- Use tmux capture-pane to monitor output
- Provide the attach command so user can interact with TFE in a new terminal
-
Launch TFE safely
# Kill any existing tfe-test session tmux kill-session -t tfe-test 2>/dev/null || true # Launch TFE in detached tmux session cd /home/matt/projects/TFE tmux new-session -d -s tfe-test -c "$PWD" "./tfe" # Verify it started tmux list-sessions | grep tfe-testThen output:
✅ TFE launched in tmux session 'tfe-test' 📋 To interact with TFE, open a new terminal and run: tmux attach -t tfe-test (Press Ctrl+B then D to detach without closing TFE) -
Ask me what feature to test
- Example: "Testing tree view expansion"
- Example: "Testing preview mode with large files"
- Example: "Testing new keyboard shortcuts"
-
Monitor during testing Use
tmux capture-pane -t tfe-test -p -S -50to capture output- Watch for panics, errors, crashes
- Check for performance issues (slow responses)
- Track any warnings or unusual output
- Parse TFE's TUI to see what file/directory is selected
-
Real-time reporting
- Alert me immediately if errors occur
- Show me the exact error and location
- Suggest what might have caused it
- Recommend fixes
- Periodically capture pane to see current state
-
Post-test analysis
- Summarize what happened during the test
- List any issues found
- Suggest improvements
- Offer to create TODO items for bugs found
-
Interactive debugging
- If a crash occurs, read the relevant source files
- Analyze the problematic code path
- Suggest fixes
- Ask if I want to apply them and re-test
- Can kill and restart TFE session as needed
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.
- 6d ago First seen · 82 lines · 9 tokens per session scan A 5a5a172cb5f7
test-tfe-feature is a command published in the GitHub repository GGPrompts/TFE (20 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 633 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-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
强制执行测试驱动开发工作流。首先搭建接口，生成测试，然后从实现能通过测试的最小代码。确保 80%+ 的覆盖率。.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.