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/obannpx skills add fullstack-phoenix/saas_kit --skill obangit 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.00045 | $0.01378 |
| Opus 5 | $0.00023 | $0.00689 |
| Sonnet 5 | $0.00009 | $0.00276 |
| Haiku 4.5 | $0.00005 | $0.00138 |
Grade A, and why
oban 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Oban background jobs
Integrates Oban, the database-backed job processing library, into the Phoenix app.
Adds the oban + oban_web deps, four queues (default, mailers, high,
low), the Pruner and Cron plugins, the oban_jobs migration, the Oban Web
dashboard, and test helpers wired into :manual mode. This is a core feature.
When to use
- The app needs to run work outside the request cycle: sending email, calling third-party APIs, generating reports, processing uploads.
- You need scheduled/recurring jobs (cron) or reliable retries with persistence.
- You want a dashboard to inspect, retry, and cancel jobs.
- Don't reach for this if a fire-and-forget
Taskis enough and you don't need persistence, retries, or scheduling.
Dependencies
- Requires: None.
- Recommended: None. If
authentication/admin is installed, the installer mounts the dashboard at/admin/oban; otherwise it mounts under/dashboard.
Install
mix saaskit.feature.install oban
No interactive decisions. The installer:
- Adds
{:oban, "~> 2.20.0"}and{:oban_web, "~> 2.11.0"}tomix.exs. - Picks the Oban engine from the boilerplate's DB choice:
Oban.Engines.Litefor sqlite3,Oban.Engines.Basicotherwise. - Mounts the Oban Web dashboard at
/admin/oban(admin present) or/dashboard.
What it generates
config/config.exs—config :my_app, Obanblock (engine, repo, queues, plugins).config/test.exs—config :my_app, Oban, testing: :manual.lib/my_app/application.ex—{Oban, Application.fetch_env!(:my_app, Oban)}in the supervision tree, after the Endpoint.lib/my_app_web/router.ex—import Oban.Web.Routerand anoban_dashboardroute.- migration
priv/repo/migrations/*_add_oban_jobs_table.exs—Oban.Migration.up(version: 12), creates theoban_jobstable. test/support/conn_case.exandtest/support/data_case.ex—use Oban.Testing, repo: MyApp.Repo.
Configuration
Injected into config/config.exs:
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 · 143 lines · 45 tokens per session scan A 1941b03bd847
oban is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 1,378 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…