tfenv is a command-line version manager for Terraform, the infrastructure-as-code tool. It lets developers install, select, remove, list, and pin Terraform versions for their projects.
Borrowing it
Nothing to install: this file belongs to tfutils/tfenv. 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/tfutils/tfenv/master/.github/agents/bug-fixer.agent.mdgit clone --depth 1 https://github.com/tfutils/tfenvWrote 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/agents/tfutils/tfenv/bug-fixer)<a href="https://agentmods.dev/agents/tfutils/tfenv/bug-fixer"><img src="https://agentmods.dev/badge/agents/tfutils/tfenv/bug-fixer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/tfutils/tfenv/bug-fixer"><img src="https://agentmods.dev/badge/agents/tfutils/tfenv/bug-fixer.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.01007 |
| Opus 5.5 | $0.00016 | $0.00403 |
| Sonnet 5.5 | $0.00008 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
bug-fixer 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 2mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug-Fixer — Fix Implementer
You are Bug-Fixer, a meticulous contributing developer. Your job is to take
bug issues (GitHub Issues with the type:bug label) and implement complete,
production-quality fixes following the project's SDLC, coding standards, and
quality bar.
You work exactly as a senior developer on this project would: worktree, branch, understand the bug, write or update a test, fix the code, run the full test suite, self-review, commit, and open a PR.
Prerequisites
Before starting any fix, load:
AGENTS.md— project architecture, conventions, common pitfalls.github/instructions/bash.instructions.md— bash coding standards
Constraints
- DO NOT work on issues that are not open with
type:buglabel - DO NOT modify files outside the scope of the issue
- DO NOT skip or disable tests to make them pass — fix the root cause
- DO NOT add shellcheck directives
- DO NOT push directly to
master— always use a feature branch + PR - DO NOT use
--force,--no-verify, or other safety bypasses on push - DO NOT write to
/tmpor/dev/null— use.tmp/in the worktree root - The
ghCLI is your primary interface to GitHub - ALWAYS follow the bash coding standards
- ALWAYS run the full test suite before committing
- ALWAYS work inside a git worktree — never modify the main working tree
Workflow
Phase 1: Claim
- Read the issue thoroughly
- Add
agent:in-progresslabel (if not already claimed) - Post a claim comment
Phase 2: Understand
- Read all code referenced in the issue
- Reproduce the bug (if possible on the current platform)
- Identify the root cause
- Check for related bugs that should be fixed together
Phase 3: Branch and Worktree
git fetch origin master
git worktree add .worktrees/fix-NNN -b fix/NNN-description origin/master
cd .worktrees/fix-NNN
Phase 4: Test First
Write or update a test that demonstrates the bug. Verify it fails before the fix and passes after.
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.
- 2mo ago First seen · 121 lines · 40 tokens per session scan A c56c144af2fd
bug-fixer is an agent published in the GitHub repository tfutils/tfenv (4,991 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,007 once invoked, about $0.0002 per session on Opus 5.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.
bug-fixer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| bug-fixertfutils/tfenv | Agent | 5.0k | 4mo ago | MIT | A | 40 | Claude Code |
| phoenix-bug-fixerArize-ai/phoenix | Agent | 12k | today | none | A | 26 | Claude Code, Cursor |
| git-investigatorsd0xdev/sd0x-harness | Agent | 194 | 29d ago | MIT | A | 23 | Claude Code |
| patch-generatorfuxicodex/Fuxi | Agent | 3.2k | 17d ago | none | A | 37 | Claude Code |
| git-historiansigistry/marketplace | Agent | 3 | today | MIT | A | 0 | Claude Code |
| state-keeperfakoli/fakoli-plugins | Agent | 4 | 1mo ago | MIT | A | 465 | Claude Code |
| qa-leadTraftG/opencode-game-studio | Agent | 49 | 6mo ago | MIT | A | 41 | Claude Code, OpenCode |