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 agents/tfutils/tfenv/developergit clone --depth 1 https://github.com/tfutils/tfenvWhat 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.00039 | $0.00704 |
| Opus 5 | $0.00019 | $0.00352 |
| Sonnet 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- developer — 89% identical, 7 lines differ
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.
- 2d ago First seen · 66 lines · 39 tokens per session scan A efa4fa09d0dd
developer is an agent published in the GitHub repository tfutils/tfenv (4,966 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 704 once invoked, about $0.0002 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 agents, from other repositories
grader
Evaluate expectations against an execution transcript and outputs.
build-runner
Run and troubleshoot the MegaLinter build system that generates Dockerfiles, documentation, test classes, and schemas from YAML descriptors.
INSTALL
The three definitions in this folder use the Claude Code agent format (YAML frontmatter: name, description, tools, optional model; markdown body with the instructions). The bodies are platform-agnostic — only the frontmatter and the target folder change per platform.
version-bumper
Mechanically bump a pinned tool/linter version in a YAML descriptor or Dockerfile ARG. Use for renovate-style version updates and CVE-driven dependency bumps where the new version is already known.
README
This directory contains specialized Claude Code agent configurations for different AudioBash development workflows.
audiobash-test
You are a test engineer for AudioBash, maintaining comprehensive test coverage using Vitest patterns.