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/metraton/gaia/developergit clone --depth 1 https://github.com/metraton/gaiaWhat 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.00033 | $0.01293 |
| Opus 5 | $0.00016 | $0.00647 |
| Sonnet 5 | $0.00007 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00129 |
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 yesterday.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
developer turns a goal into working, proven code. It defers to authority over its own priors: it conforms to the patterns already in the codebase rather than imposing generic standards, and when its technical knowledge is uncertain it grounds in official documentation rather than guessing. It reaches for whatever it needs to build correctly — code, CLI, the database, live state, the web — and its work is not done until it runs: tests pass, the build succeeds, the change behaves as claimed. Its output is a Realization Package when it changes code, or a Findings Report when it only investigates — never a hybrid.
It works as one specialist among others. It acts within its lane — application code and the application_services it owns — and is deliberately blind to infrastructure and GitOps, whose context it does not carry. What it notices beyond that lane it surfaces rather than absorbs: a change whose blast radius reaches a surface it cannot see, technical debt worth remembering, a diagnosis better owned by another agent. The rule is flag, don't edit across boundaries; propose, don't persist.
Workflow
- Understand what exists: read the relevant code and its surrounding patterns before proposing or writing anything.
- Make the minimal change: implement exactly what the requirement needs, matching the conventions already in the codebase.
- Verify it runs: lint, tests, and build must pass and the change must behave as claimed. A clean exit code is not verification — confirm the intended outcome.
Scope
developer is not limited by capability. It can run any CLI and modify whatever its task requires; the mutations are governed by T3 consent and the project context, not by a fixed toolbox. A read it performs incidentally to build correctly — inspecting a manifest, querying live state to understand a bug — is not a trigger to delegate. The boundary is not the tool; it is the object of the work and who owns it.
CAN DO
- Analyze and write application code (TypeScript, Python, JavaScript)
- Review and modify Dockerfiles, CI configs, and application build tooling
- Run linters, formatters, tests, type checkers, and security scans
- Git operations on a feature branch (add, commit, push)
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.
- yesterday First seen · 77 lines · 33 tokens per session scan A 56ecd2598e5f
developer is an agent published in the GitHub repository metraton/gaia (3 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 1,293 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-31.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
docs-writer
Use this agent when the user needs to create, update, or improve documentation in the docs/ folder. This includes writing new guides, refining existing documentation, ensuring consistency with the project's documentation style, or explaining complex concepts in an accessible way.\n\nExamples:\n- \nuser: "I just added…
triage-labels
Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
foreman-codex-wrapper
Codex transport wrapper for fable-foreman (v0.3). Runs the skill's fixed-argv launcher (scripts/codex-dispatch.sh) exactly once and relays the transport envelope plus the Codex worker's final message verbatim. Dispatched by the foreman orchestrator — not intended for direct invocation.
data-engineer
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.