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/setup-tfe-logginggit 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/setup-tfe-logging)<a href="https://agentmods.dev/commands/ggprompts/tfe/setup-tfe-logging"><img src="https://agentmods.dev/badge/commands/ggprompts/tfe/setup-tfe-logging.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.00011 | $0.01115 |
| Opus 5 | $0.00005 | $0.00558 |
| Sonnet 5 | $0.00002 | $0.00223 |
| Haiku 4.5 | $0.00001 | $0.00112 |
Grade A, and why
setup-tfe-logging 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup TFE Event Logging
You are adding debug event logging to TFE so I can monitor what's happening in the application in real-time.
Your Task
Add a debug logging system to TFE that logs events to /tmp/tfe-events.jsonl.
Step 1: Add Debug Logger to Model
Edit types.go to add a debug log file handle:
type model struct {
// ... existing fields ...
debugLog *os.File // Add this field
}
Step 2: Create Debug Helper
Create or edit helpers.go to add logging functions:
func (m *model) enableDebugLogging() error {
var err error
m.debugLog, err = os.OpenFile("/tmp/tfe-events.jsonl",
os.O_CREATE|os.O_WRONLY|os.O_APPEND, 0644)
return err
}
func (m *model) logEvent(event string, data interface{}) {
if m.debugLog == nil {
return
}
entry := map[string]interface{}{
"time": time.Now().Format("15:04:05.000"),
"event": event,
"data": data,
}
json.NewEncoder(m.debugLog).Encode(entry)
}
func (m *model) closeDebugLog() {
if m.debugLog != nil {
m.debugLog.Close()
}
}
Step 3: Initialize Logger
Edit model.go in the initialModel() function:
func initialModel() model {
m := model{
// ... existing initialization ...
}
// Enable debug logging if TFE_DEBUG env var is set
if os.Getenv("TFE_DEBUG") == "1" {
m.enableDebugLogging()
}
return m
}
Step 4: Add Logging Calls
Add strategic logging calls throughout the codebase:
In file_operations.go:
func (m *model) loadPreview(path string) {
m.logEvent("preview_load_start", map[string]string{"path": path})
// ... existing code ...
m.logEvent("preview_loaded", map[string]interface{}{
"path": path,
"size": len(content),
"lines": strings.Count(content, "\n"),
})
}
func (m *model) loadFiles(path string) ([]fileItem, error) {
m.logEvent("load_directory", map[string]string{"path": path})
// ... existing code ...
m.logEvent("directory_loaded", map[string]interface{}{
"path": path,
"file_count": len(files),
})
return files, nil
}
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 · 178 lines · 11 tokens per session scan A ac0e479ad550
setup-tfe-logging is a command published in the GitHub repository GGPrompts/TFE (20 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 1,115 once invoked, about $0.0001 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
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.