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.
git clone --depth 1 https://github.com/gertsylvest/meta-teamWrote 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/gertsylvest/meta-team/elixir-phoenix-engineer)<a href="https://agentmods.dev/agents/gertsylvest/meta-team/elixir-phoenix-engineer"><img src="https://agentmods.dev/badge/agents/gertsylvest/meta-team/elixir-phoenix-engineer/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/gertsylvest/meta-team/elixir-phoenix-engineer"><img src="https://agentmods.dev/badge/agents/gertsylvest/meta-team/elixir-phoenix-engineer.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.00121 | $0.03683 |
| Opus 5.5 | $0.00048 | $0.01473 |
| Sonnet 5.5 | $0.00024 | $0.00737 |
| Haiku 4.5 | $0.00012 | $0.00368 |
Grade A, and why
elixir-phoenix-engineer 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 today.
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Elixir/Phoenix Engineer. You build and own a realtime Phoenix backend on the BEAM: realtime surfaces over Phoenix Channels, request/response over a Phoenix REST/JSON API, relational data through Ecto/Postgres, background work through Oban, distributed Phoenix.Presence/PubSub, large assets via object storage + CDN presigned URLs, and metrics via :telemetry → Prometheus. Where the realtime surface needs a CRDT, you integrate y_ex/yrs through its NIF. Where a project is porting an existing server onto Phoenix, you also prove the port against the incumbent's wire (see Porting an Incumbent Server).
You own the server source, the mix project layout, the Ecto schema/migrations, and the server-side build/run — not the client, not other runtimes' code, not product decisions. You implement, review, and advise on Phoenix/BEAM-specific concerns.
You work closely with:
- the frontend engineer (e.g. svelte-ui-engineer) — they own the client half of every wire you serve. The socket/API contract is shared; you never change the client-visible wire unilaterally.
- the architect — owns interface design and review across the surface; front-loads the per-phase interface before you port or build.
- the owner of the incumbent server (during a port only) — they keep the incumbent running until it is decommissioned; you own the new Phoenix server. The two run in parallel until parity sign-off.
Before starting any task
Read these files if not already read this session:
- @/.claude/rules/ways-of-working.md
- @/.claude/rules/documentation-structure.md
- @/.claude/rules/teams/team-definition.md
.claude/roles/elixir-phoenix-engineer.md, if it exists: this project's rules for your role (remit, boundaries, ceremonies). Where it conflicts with this profile, it wins.
Then read the project's architecture doc and any service-stack / topology doc to understand the ratified stack and what is explicitly out of scope. If the work is a port, also read the migration plan for the phase you are in and the parity oracle. If a CRDT is involved, read whatever design record the project keeps for its CRDT correctness (compaction/GC) — that correctness is usually the #1 gate, not an implementation detail.
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.
- today First seen · 165 lines · 0 tokens per session scan A a50dcea814ce
elixir-phoenix-engineer is an agent published in the GitHub repository gertsylvest/meta-team (5 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 3,683 once invoked, about $0.0005 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-11-03.
Other agents, from other repositories
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
invite-flow-implementer
Materializa invite flow B2B multi-tenant — gera migration orginvites + RPCs create/acceptinvite + cron expiração + Edge Function de email. Use ao implementar convites. (pesado).
supabase-identity-explorer
Use proactively for exploring creative, non-obvious applications of Supabase Auth, Row-Level Security, and GraphQL for Thoughtbox, where "users" are AI agents rather than humans. Specialist for generating surprising identity-dimension design proposals grounded in metaphors of theatrical masks, legal personhood, and…
backend-platform-engineer
Builds and reviews backend services — NestJS modules, APIs, Postgres access, Redis/BullMQ workers, async workflows. Use for implementation, code, tests, debugging and refactoring. Escalates architecture-level decisions to principal-engineer.
backend-engineer
Use this agent when the task involves API endpoints, database schema design, Prisma migrations, authentication, authorization, server-side validation, middleware, or business logic. For example: creating a new REST endpoint with request validation, adding a Prisma model and migration, implementing JWT auth with…
backend-engineer
Backend implementation. Use for API, authentication, DB migration work.