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 spinspire/pocketbase-sveltekit-starter --skill pb-apigit clone --depth 1 https://github.com/spinspire/pocketbase-sveltekit-starterWrote 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/spinspire/pocketbase-sveltekit-starter/pb-api)<a href="https://agentmods.dev/skills/spinspire/pocketbase-sveltekit-starter/pb-api"><img src="https://agentmods.dev/badge/skills/spinspire/pocketbase-sveltekit-starter/pb-api/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/spinspire/pocketbase-sveltekit-starter/pb-api"><img src="https://agentmods.dev/badge/skills/spinspire/pocketbase-sveltekit-starter/pb-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 6 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00031 | $0.00572 |
| Opus 5 | $0.00015 | $0.00286 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
pb-api scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash, curl What it actually says
PocketBase API
Reference: https://pocketbase.io/docs/
Operate PocketBase via its REST API.
Credentials
Create .env from .env.example (never commit .env):
PB_URL=http://localhost:8090
[email protected]
PB_SUPERUSER_PASSWORD=your-password
If credentials aren't available via env vars, ask user explicitly before proceeding.
Quick Start
# Auth
curl -X POST http://localhost:8090/api/collections/_superusers/auth \
-H 'Content-Type: application/json' \
-d '{"identity":"[email protected]","password":"secret"}'
# List records
curl http://localhost:8090/api/collections/posts/records \
-H 'Authorization: Bearer TOKEN'
# Filter records
curl "http://localhost:8090/api/collections/posts/records?filter=status='published'&sort=-created&expand=author"
Key Endpoints
| Method | Endpoint | Purpose |
|---|---|---|
| POST | /api/collections/:collection/auth |
Auth with password |
| POST | /api/collections/:collection/auth-with-password |
Login |
| GET | /api/collections/:collection/records |
List records |
| POST | /api/collections/:collection/records |
Create record |
| PATCH | /api/collections/:collection/records/:id |
Update record |
| DELETE | /api/collections/:collection/records/:id |
Delete record |
Filter Syntax
status = 'published'
author.id = 'abc123'
created >= '2024-01-01'
user.name ~ 'john*'
Use @collection.name.field for cross-collection filters.
SDK Usage
import PocketBase from 'pocketbase'
const pb = new PocketBase('http://localhost:8090')
await pb.collection('posts').authWithPassword('[email protected]', 'secret')
// List with filter
const records = await pb.collection('posts').getList(1, 50, {
filter: "status = 'published'",
sort: '-created',
expand: 'author,tags'
})
API Rules
null→ superuser only""→ public access- Start locked, open selectively
- Use
@request.auth,@collection,@nowin rules
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.
- 9d ago First seen · 86 lines · 31 tokens per session scan A c336b6a22927
pb-api is a skill published in the GitHub repository spinspire/pocketbase-sveltekit-starter (508 stars, last pushed 17d ago), licensed MIT. It adds 31 tokens to every session and 572 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
new-entity
Create a backend entity with EF Core configuration and migration.
pocketbase-best-practices
PocketBase development best practices covering collection design, API rules, authentication, SDK usage, query optimization, realtime subscriptions, file handling, deployment, and server-side extending (Go + JSVM). Current as of PocketBase v0.40 and JS SDK v0.28. Use when building PocketBase backends, designing…
svelte-advanced-datatable-data
Pick and wire a DataTable data source (LocalDataSource, FetchApiDataSource, ApiFunctionDataSource, SvelteQueryDataSource, custom AbstractDataSource/IDataSource), configure basic vs advanced search (BasicTextSearchParser, AdvancedSearchParser with key:value filters /.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…