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 skills/fullstack-phoenix/saas_kit/teamsnpx skills add fullstack-phoenix/saas_kit --skill teamsgit clone --depth 1 https://github.com/fullstack-phoenix/saas_kitWhat 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.00041 | $0.01312 |
| Opus 5 | $0.00020 | $0.00656 |
| Sonnet 5 | $0.00008 | $0.00262 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
teams 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teams
Adds multi-tenancy on top of authentication. Every user automatically gets a
personal team on registration, can belong to additional shared teams via
memberships, and can switch the active team. The Scope struct in
lib/my_app/users/scope.ex carries both current_user and current_team, so
queries can be isolated per tenant. Ships team-management and member LiveViews
plus a team switcher component.
When to use
- The app needs multi-user accounts where data is owned by a team, not a single user (shared workspaces, organizations, projects).
- You want role-based membership (
:owner/:member) and an invite flow out of the box. - Don't reach for this if the app is single-user —
authenticationalone is enough. Teams adds a scoping discipline you must follow everywhere.
Dependencies
- Requires:
authentication(this is acorefeature,position6 — install it after auth). - Recommended: None.
Install
mix saaskit.feature.install teams
No interactive decisions. The installer generates the Teams context, schemas,
and LiveViews; wires current_team into UserAuth/Scope; adds the :team
scope to config; and (when the layouts feature is present) injects a Teams
nav link and the team switcher into the app and public layouts.
What it generates
lib/my_app/teams.ex— context:create_team/2,update_team/2,create_membership/3,list_memberships/1,create_invitation/3,can_be_accessed_by_a_user?/2.lib/my_app/teams/team.ex—teamsschema (name,personal,created_by).lib/my_app/teams/membership.ex—team_membershipsjoin (roleenum).lib/my_app/teams/member.ex— read view onto theuserstable for membership.lib/my_app/teams/invitation.ex+invitation_notifier.ex— email invites.lib/my_app_web/live/team_live/andmember_live/— management LiveViews.lib/my_app_web/live/team_switch_component.ex— header team switcher.- Extends
lib/my_app/users/user.exwithcurrent_team_id,personal_team,memberships,teams, andlib/my_app/users.exwithswitch_team/2,current_team/1,with_memberships/1, auto personal-team creation on register. - Migration
priv/repo/migrations/*_create_teams_migrations.exs—teams,team_memberships,invitationstables.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 135 lines · 41 tokens per session scan A 8a7b96d54c38
teams is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,312 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…