Dev · Team of 3 roles

Security review

Codex audits and lists the flaws by severity; Claude fixes the high and medium ones, with tests; Codex checks each one.

How the work flows

Security auditor → Security fixes → Security checker · Security checker → Security fixes (if REPROVADO, up to 2 times)

Example request: Review the login and upload routes before opening to customers

The roles

The prompts are in Portuguese; you can translate or change them after adding the recipe.

  1. Security auditorAgent: Codex · Not allowed: push
    See the prompt
    Antes de começar, leia as regras do projeto (CLAUDE.md, AGENTS.md ou README) e siga o jeito do código que já existe. Revise a parte pedida procurando falhas de segurança: entrada sem validação, autorização faltando, injeção, segredo no código, upload sem limite, dado pessoal em log ou mensagem de erro. Liste em seguranca.md, por gravidade (alta, média, baixa), com o arquivo, a linha e como explorar. Não invente: só o que dá para mostrar no código. Não mexa no código: grave só seguranca.md.
    Termine com uma linha PRONTO: e o resumo do que entregou.
  2. Security fixesAgent: Claude · Not allowed: push
    See the prompt
    Antes de começar, leia as regras do projeto (CLAUDE.md, AGENTS.md ou README) e siga o jeito do código que já existe. Corrija os itens de gravidade alta e média de seguranca.md, cada um com um teste que prove a correção. Os de gravidade baixa ficam anotados. Faça commit.
    Termine com uma linha PRONTO: e o resumo do que entregou.
  3. Security checkerAgent: Codex · Not allowed: editar, push
    See the prompt
    Confira cada item de gravidade alta e média de seguranca.md: foi corrigido de verdade e tem teste?
    Não corrija nada. Responda APROVADO ou REPROVADO, com a lista do que mudar.

How to use it in Fleetly

  1. Create your account and connect a machine with Claude Code, Codex, Antigravity or GitHub Copilot.
  2. With recipes enabled: Teams → Recipes, open this one and tap Use in my building. The new team wizard opens already set up; pick the folder and who takes each seat.
  3. By hand: in Roles, create one role for each with the prompt above; in Teams, create the team and connect the arrows as in the flow.
Create account

More Dev recipes

DevTeam of 2 rolesOne builds, the other reviewsClaude builds the server side; Codex reviews the diff. If it fails, it goes back up to 2 times.DevTeam of 4 rolesFull featureThe PO writes the spec; backend and frontend build it; Codex reviews against the acceptance criteria. If it fails, it goes back to frontend.DevTeam of 4 rolesBug dutyTriage decides: TELA (screen) goes to frontend, API to backend. Then the tests (Codex) confirm the problem is gone and nothing broke.DevTeam of 4 rolesNew screenThe PO writes the spec; frontend builds it; QA uses the screen in the browser like a person would; the interface reviewer checks states, phone and accessibility. If it fails, it goes back to frontend.DevTeam of 5 rolesBig changeThe architect writes the plan; backend and frontend build it; Codex reviews; technical docs close it with README and changelog.DevTeam of 3 rolesDatabase migrationThe database change without data loss, the code that uses the new schema and Codex’s review, with the plan to undo it.DevTeam of 3 rolesTests for a project without testsOne maps the riskiest parts, another writes the tests, the third checks they run and test what matters.DevRoutineNightly reviewMonday to Friday at 10 pm, reads what changed that day and points out problems, without touching the code.Monday to Friday, at 22:00DevRoutineTests every morningBefore you arrive, runs the tests and checks and fixes what fails, in a worktree.Monday to Friday, at 06:30DevRoutineDependencies up to dateEvery Monday, updates the minor dependencies if the build and tests pass, and lists the major ones for you to decide.Monday, at 07:00