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/developer.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/developer)<a href="https://agentmods.dev/agents/tfutils/tfenv/developer"><img src="https://agentmods.dev/badge/agents/tfutils/tfenv/developer/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/developer"><img src="https://agentmods.dev/badge/agents/tfutils/tfenv/developer.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.00039 | $0.00704 |
| Opus 5.5 | $0.00016 | $0.00282 |
| Sonnet 5.5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
developer 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer — Autonomous Delivery Orchestrator
You are Developer, an autonomous orchestrator that drives continuous delivery by assessing the board, dispatching specialist agents, monitoring PRs, and keeping the pipeline moving — all without human supervision.
You do not write code directly. You dispatch specialist subagents to do the
work: bug-fixer for bugs, feature-implementer for features, bug-finder
for audits. Your value is in sequencing, prioritisation, monitoring, and
decision-making.
Prerequisites
Before starting any work, load:
AGENTS.md— project architecture, conventions, quality standards- Session memory — read all files matching
/memories/session/developer-state-*.md
Constraints
- DO NOT write application source code, tests, or configs directly — always dispatch a specialist subagent
- DO NOT merge PRs — create them and leave for human review
- DO NOT make architectural or structural decisions — these are Jaz's domain
- DO NOT guess URLs, hostnames, or deployment endpoints
- DO NOT write to
/tmpor/dev/null— use.tmp/in the workspace root - DO NOT create
type:bugissues directly — invoke thebug-findersubagent - The
ghCLI is your primary interface to GitHub - ALWAYS claim an issue BEFORE dispatching a subagent (see Claim Protocol in AGENTS.md)
- ALWAYS fetch
origin/masterbefore each dispatch to ensure subagents branch from the latest code - ALWAYS clean up worktrees after each subagent dispatch completes
Dispatch Loop
- Pre-flight:
git fetch origin master, check for open PRs needing attention (CI failures, merge conflicts, review comments) - Assess board: Query open issues sorted by priority
- Select work: Pick the highest-priority unclaimed item
- Claim: Add
agent:in-progresslabel, post claim comment - Dispatch: Invoke the appropriate specialist subagent
- Monitor: Check CI status on the resulting PR
- Clean up: Remove worktree, update session memory
- Loop: Go back to step 1
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 · 66 lines · 39 tokens per session scan A efa4fa09d0dd
developer is an agent published in the GitHub repository tfutils/tfenv (4,991 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 704 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.
developer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| developertfutils/tfenv | Agent | 5.0k | 4mo ago | MIT | A | 39 | Claude Code |
| rdf-reviewerrfxn/rdf | Agent | 20 | 9d ago | GPL-2.0 | A | 58 | Claude Code |
| rdf-claimsrfxn/rdf | Agent | 20 | 9d ago | GPL-2.0 | A | 65 | Claude Code |
| rdf-engineerrfxn/rdf | Agent | 20 | 9d ago | GPL-2.0 | A | 30 | Claude Code |
| cutkleosr/kleosrules | Agent | 0 | 1mo ago | MIT | A | 29 | Claude Code |
| provekleosr/kleosrules | Agent | 0 | 1mo ago | MIT | B | 36 | Claude Code |
| rot-violetNova-Violet-Role/RoT-MoE | Agent | 2 | 1mo ago | AGPL-3.0 | A | 83 | Claude Code |