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 skills add fullstack-phoenix/saas_kit --skill invitationsgit clone --depth 1 https://github.com/fullstack-phoenix/saas_kitWrote 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/skills/fullstack-phoenix/saas_kit/invitations)<a href="https://agentmods.dev/skills/fullstack-phoenix/saas_kit/invitations"><img src="https://agentmods.dev/badge/skills/fullstack-phoenix/saas_kit/invitations/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/skills/fullstack-phoenix/saas_kit/invitations"><img src="https://agentmods.dev/badge/skills/fullstack-phoenix/saas_kit/invitations.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.00036 | $0.00724 |
| Opus 5.5 | $0.00014 | $0.00290 |
| Sonnet 5.5 | $0.00007 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00072 |
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 2mo 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.
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.mdfirst 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
Invitationschema has adeclined_atfield — set it viaupdate_invitation/2instead of creating a membership.
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.
- 2mo ago First seen · 89 lines · 36 tokens per session scan A 57e1c5a9044f
invitations is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 724 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dev-runtime
How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…