agentmods.dev

api-platform-user

A reusable recipe for adding authenticated users to an API Platform 4.3 and Symfony 7.4+ application. It covers registration, password storage, the signed-in user’s profile, and the `/me` endpoint, which returns the current user.

In plain words
What is it for?
Use it when starting user accounts or adding registration and self-profile updates to an API. It supports REST and GraphQL access, validation, password hashing, and tests with a faster test-only hashing setup.
Why use it?
It lays out the security rules needed to avoid exposing passwords or accepting unsafe profile changes. It also keeps password hashing and automatic password upgrades in one defined workflow.

Skill for Claude CodeCodex

Part of the gerard plugin — 25 skills, 25 commands, 7 agents, 1 hook shipped together

2 3mo ago A scan 196 tokens original MIT
View the source file gerard-labs/superpowers-api-platform
Install

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.

agentmods
npx agentmods add skills/gerard-labs/superpowers-api-platform/api-platform-user
Any agent
npx skills add gerard-labs/superpowers-api-platform --skill api-platform-user
Clone the repo
git clone --depth 1 https://github.com/gerard-labs/superpowers-api-platform

Made for: Claude Code, Codex.

Or install gerard, the plugin that ships this one along with the rest of its 25 skills, 25 commands, 7 agents, 1 hook.

Per session 196 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 723 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00196 $0.00723
Opus 5 $0.00098 $0.00362
Sonnet 5 $0.00039 $0.00145
Haiku 4.5 $0.00020 $0.00072

Measured 2d ago against content hash a1296e21f579, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

api-platform-user 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 2d 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.

skills/api-platform-user/SKILL.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

API Platform 4.3 — User entity (UserInterface, password hashing, /me)

Use when

  • Bootstrapping a new project that needs authenticated users.
  • Adding registration (POST /api/users open) + self-profile updates (PUT /api/users/{id} constrained to object == user).
  • Exposing the current authenticated user via /me.
  • Adopting auto-rehashing when the password hashing algorithm evolves.

Default workflow

  1. Implement User implements UserInterface, PasswordAuthenticatedUserInterface. Persist $password (hashed), keep $plainPassword transient.
  2. Apply #[UniqueEntity('email')] + Default + user:create validation context on the POST operation.
  3. Write the UserPasswordHasher State Processor that decorates persist_processor and hashes $plainPassword, then nukes it from memory.
  4. Implement PasswordUpgraderInterface in the Repository for transparent rehashing.
  5. Add the /me endpoint via a CurrentUserProvider (Provider-based, REST + GraphQL compatible).
  6. Configure md5 hashing only in config/packages/test/security.yaml to speed the test suite ×5.

Guardrails

  • $password is NEVER in a serialization group. It must not appear in any response.
  • $plainPassword is NEVER persisted (no #[ORM\Column]), only validated on user:create.
  • Hashing in the Processor, not in the controller — that's the canonical 4.x pattern.
  • /me via Provider, not Controller — for REST + GraphQL compatibility.
  • Hash-light in tests only — never in any other environment.

Progressive disclosure

  • SKILL.md covers posture and rules.
  • reference.md carries the full entity, Processor, Repository with PasswordUpgraderInterface, /me Provider, test hashing config, and best practices.

Output contract

  • A User entity following the canonical pattern.
  • A UserPasswordHasher Processor that hashes and nukes $plainPassword.
  • A UserRepository implements PasswordUpgraderInterface for auto-rehashing.
  • A /me endpoint backed by CurrentUserProvider.
  • Test-only password hashing config in config/packages/test/security.yaml.

Read the full file on GitHub · 49 lines

Files

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.

Changes

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.

  1. 2d ago First seen · 49 lines · 196 tokens per session scan A a1296e21f579

Subscribe to this mod's changes

api-platform-user is a skill published in the GitHub repository gerard-labs/superpowers-api-platform (2 stars, last pushed 3mo ago), licensed MIT. It adds 196 tokens to every session and 723 once invoked, about $0.0010 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.

Backend and APIsapiapi-platformclaudeclaude-codeclaude-code-pluginsymfony
Related

Other skills, from other repositories

server-setup

Initialize tRPC with initTRPC.create(), define routers with t.router(), create procedures with .query()/.mutation()/.subscription(), configure context with createContext(), export AppRouter type, merge routers with t.mergeRouters(), lazy-load routers with lazy().

trpc/trpc · 56 tokens

client-setup

Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.

trpc/trpc · 63 tokens

non-json-content-types

Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).

trpc/trpc · 75 tokens

caching

Set HTTP cache headers on tRPC query responses via responseMeta callback for CDN and browser caching. Configure Cache-Control, s-maxage, stale-while-revalidate. Handle caching with batching and authenticated requests. Avoid caching mutations, errors, and authenticated responses.

trpc/trpc · 54 tokens

portaljs-connect-ckan

Wire a scaffolded PortalJS portal to a CKAN backend over its API. Generates a tiny server-side fetch client (no runtime dependency) and feeds the /search catalog and /@namespace/slug showcases from CKAN instead of datasets.json. Use when connecting an existing portal to a live CKAN instance instead of a static…

datopian/portaljs · 74 tokens

horse-grpc

Guidelines and workflows for developing and maintaining gRPC services, HTTP/2 h2c transport, and Protobuf serialization within the Horse framework.

HashLoad/horse · 33 tokens