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 suxrobGM/jobpilot --skill add-api-routegit clone --depth 1 https://github.com/suxrobGM/jobpilotWrote 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/suxrobgm/jobpilot/add-api-route)<a href="https://agentmods.dev/skills/suxrobgm/jobpilot/add-api-route"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/add-api-route.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.00321 |
| Opus 5 | $0.00023 | $0.00161 |
| Sonnet 5 | $0.00009 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
add-api-route 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 8d 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.
What it actually says
Add an API route
Follow the conventions in .claude/rules/api.md (response schemas, z.date(), global error
envelope). Steps:
- Request schema: reuse or add in
packages/contracts(or the module's<name>.schema.ts). Uuid path ids viaidParam. - Response schema: model the service's return exactly in
<name>.schema.ts, or use a shared envelope from@/types/response. Elysia strips fields not in the schema. - Route: in
modules/<name>/<name>.controller.ts, addbody/query/paramsas needed, theresponsesuccess schema, adetailsummary, and arateLimit(policy)beforeHandlewhere the endpoint warrants one. No per-route error responses - they're declared globally. - Logic in
<name>.service.ts(tsyringe@singleton; injected classes stay value imports). New module: mirror an existing one and mount its controller inapp.ts. - Web side (if needed): Eden Treaty picks up types automatically; add query/mutation hooks
under
apps/web/src/api/. - Invoke the
verifyskill.
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.
- 8d ago First seen · 23 lines · 46 tokens per session scan A 24a5bb011596
add-api-route is a skill published in the GitHub repository suxrobGM/jobpilot (65 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 321 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-30.
Other skills, from other repositories
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
oban
Oban job processing — workers, perform/1 (OSS) and process/1 (Pro), queues, cron, retries, unique jobs, idempotency, Oban Pro (Workflow, Batch, Chunk, Smart Engine), Testing. Use when writing Oban workers, queue config, or debugging jobs.
perf
Analyze Elixir/Phoenix performance — N+1 queries, assign bloat, ecto optimization, genserver bottlenecks. Use when slowness, timeouts, or high memory reported.