security

Security guidance covering authentication and access control in a specific application setup. Authentication checks who a user is, while access control checks what that user may view or change.

In plain words
What is it for?
Use it when reviewing or changing login-related code, protected server procedures, and user-data access.
Why use it?
It identifies insecure public data procedures and shows the intended protected approach for user data.

Skill for Claude CodeCodex

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/rekabytes/opencode-skills/security
Any agent
npx skills add rekabytes/opencode-skills --skill security
Clone the repo
git clone --depth 1 https://github.com/rekabytes/opencode-skills

Made for: Claude Code, Codex.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,088 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.00017 $0.03088
Opus 5 $0.00009 $0.01544
Sonnet 5 $0.00003 $0.00618
Haiku 4.5 $0.00002 $0.00309

Measured yesterday against content hash 374cb41df90d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security 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.

templates/skills/security/SKILL.md · 458 lines

How it starts

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

Security Patterns

1. Authentication

Current State

  • Frontend: Logto (OAuth/OIDC) handles user sessions
  • Backend: protectedProcedure exists but NEVER used
  • All 15 routers use publicProcedure (INSECURE for user data)

Code: protectedProcedure vs publicProcedure

// CURRENT (INSECURE) - used everywhere in this codebase
export const userRouter = router({
  getProfile: publicProcedure
    .input(z.object({ userId: z.string() }))
    .query(({ input }) => {
      // ❌ Anyone can access any user's profile!
      return prisma.user.findUnique({ where: { id: input.userId } });
    }),
});

// SHOULD BE - using protectedProcedure
export const userRouter = router({
  getMyProfile: protectedProcedure
    .query(({ ctx }) => {
      // ✅ Only authenticated users can access
      // ctx.user is guaranteed to be populated
      return prisma.user.findUnique({ where: { id: ctx.user.id } });
    }),
});

Auth Context (trpc.ts)

// Current state - ctx.user is ALWAYS null!
export const createContext = async ({ req, res }) => {
  return {
    req,
    res,
    prisma,
    user: null, // Will be populated when token verification is implemented
  };
};

// Protected procedure always throws UNAUTHORIZED
export const protectedProcedure = t.procedure.use(async function isAuthed(opts) {
  const { ctx } = opts;
  if (!ctx.user) {
    throw new TRPCError({ code: 'UNAUTHORIZED' });
  }
  return opts.next({ ctx: { user: ctx.user } });
});

Rules

  • ✅ Use protectedProcedure for any user-specific data
  • ✅ Use publicProcedure only for truly public data (game info, item catalogs)
  • ❌ NEVER use publicProcedure for: user profiles, settings, private data, mutations

2. Input Validation

Current Approach

  • Zod on ALL inputs (this is good)
  • Example patterns from codebase:
// String with length limits
z.string().min(3).max(80)
z.string().email()
z.string().uuid()
z.string().optional()

// Numbers with bounds  
z.number().min(1).max(100)
z.number().min(1).max(50).default(20)

// Booleans with defaults
z.boolean().default(false)

// Enums for fixed values
z.enum(['OPEN', 'CLOSED', 'IN_PROGRESS'])
z.enum(['RANKED', 'CASUAL', 'CUSTOM', 'TOURNAMENT'])

// Arrays
z.array(z.string())
z.array(z.string()).min(1)

// Objects with nested validation
z.object({
  user: z.object({
    id: z.string(),
    username: z.string().optional(),
    avatarUrl: z.string().optional(),
    avatarConfig: z.record(z.string(), z.any()).optional(),
    isGuest: z.boolean().default(false),
  })
})

// Nullable and optional
z.string().nullable()
z.string().optional()
z.string().optional().nullable()

Read the full file on GitHub · 458 lines

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. yesterday First seen · 458 lines · 17 tokens per session scan A 374cb41df90d

Subscribe to this mod's changes

security is a skill published in the GitHub repository rekabytes/opencode-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 3,088 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens