invitations

Instructions for adding team invitations to a Phoenix application. The flow emails a sign-in link, then adds the invitee to the team after they sign in.

In plain words
What is it for?
Use it to implement or customize team invitation emails and the process that accepts an invitation during sign-in.
Why use it?
It explains how to connect invitation records, email notifications, and membership acceptance. This avoids having to design the invite process from scratch.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/fullstack-phoenix/saas_kit/invitations
Any agent
npx skills add fullstack-phoenix/saas_kit --skill invitations
Clone the repo
git clone --depth 1 https://github.com/fullstack-phoenix/saas_kit

Made for: Claude Code, Codex.

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 724 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00036 $0.00724
Opus 5 $0.00018 $0.00362
Sonnet 5 $0.00007 $0.00145
Haiku 4.5 $0.00004 $0.00072

Measured yesterday against content hash 57e1c5a9044f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

invitations 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.

skills/teams/invitations/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Team Invitations

The teams feature ships an email invitation flow. An owner creates an Invitation for an email; a Swoosh notifier emails a sign-in link; once the invitee signs in, you turn the pending invitation into a membership.

When to use

  • A team owner needs to add members who don't yet have an account.
  • You want to customize the invite email (sender, copy, branding) or the acceptance behavior.
  • Read the parent ../SKILL.md first for install and scoping.

How it works

MyApp.Teams.create_invitation/3 inserts the invitation and pipes the result through invite_member/1, which calls the notifier:

# lib/my_app/teams.ex
def create_invitation(team, user, attrs \\ %{}) do
  %Invitation{}
  |> Invitation.changeset(attrs)
  |> Ecto.Changeset.put_assoc(:team, team)
  |> Ecto.Changeset.put_assoc(:invited_by, user)
  |> Repo.insert()
  |> invite_member()
end

The notifier sends a plain-text email with a log-in URL:

# lib/my_app/teams/invitation_notifier.ex
def invite_user_email(%{email: email, url: url}) do
  new()
  |> to(email)
  |> from({"Phoenix Team", "[email protected]"})
  |> subject("Invited to join")
  |> text_body("...#{url}...")
  |> Mailer.deliver()
end

Pending invitations for the current user are found by email:

MyApp.Teams.list_invitations_for_user(user) # email match, accepted_at IS NULL

Tweaking for your app

Customize the sender and copy in lib/my_app/teams/invitation_notifier.ex:

|> from({"Acme", "[email protected]"})
|> subject("You're invited to join #{team_name} on Acme")

Accept an invitation after the invitee signs in — create the membership, then mark the invitation accepted:

{:ok, _membership} = MyApp.Teams.create_membership(invitation.team, user, %{role: :member})

{:ok, _invitation} =
  MyApp.Teams.update_invitation(invitation, %{
    accepted_at: DateTime.utc_now() |> DateTime.truncate(:second)
  })
  • Token links: the default email links to /users/log-in. To make it one-click, pass a signed token in the URL and verify it on the acceptance page.
  • Decline: the Invitation schema has a declined_at field — set it via update_invitation/2 instead of creating a membership.

Read the full file on GitHub · 89 lines

Changes

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.

  1. yesterday First seen · 89 lines · 36 tokens per session scan A 57e1c5a9044f

Subscribe to this mod's changes

invitations is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 724 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens