junjo: Skill for Claude Code

.agents/skills/studio-security-auth/SKILL.md

studio-security-auth is a skill for Claude Code, Codex from mdrideout/junjo. It costs 35 tokens per session (697 once invoked), scanned A, original, Apache-2.0.

A workflow for reviewing or changing authentication boundaries in Junjo AI Studio. Authentication is how software verifies who is allowed to access it, including API keys, session cookies, and service-to-service checks.

In plain words
What is it for?
Use it when working on API-key validation, CORS, session cookies, internal authentication over gRPC, secret handling, or security reviews of this code.
Why use it?
It helps identify security mistakes involving credentials, browser access rules, cookie handling, middleware order, or communication between Studio services.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is mdrideout/junjo's own configuration. It tells Claude Code and Codex how to work on junjo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything junjo configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mdrideout/junjo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mdrideout/junjo/master/.agents/skills/studio-security-auth/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mdrideout/junjo

Made for: Claude Code, Codex.

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

agentmods badge for studio-security-auth

README.md
[![agentmods](https://agentmods.dev/badge/skills/mdrideout/junjo/studio-security-auth/github.svg)](https://agentmods.dev/skills/mdrideout/junjo/studio-security-auth)
Your own site
<a href="https://agentmods.dev/skills/mdrideout/junjo/studio-security-auth"><img src="https://agentmods.dev/badge/skills/mdrideout/junjo/studio-security-auth/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.

agentmods 80×15 button for studio-security-auth

Your own site · 80×15
<a href="https://agentmods.dev/skills/mdrideout/junjo/studio-security-auth"><img src="https://agentmods.dev/badge/skills/mdrideout/junjo/studio-security-auth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 697 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00035 $0.00697
Opus 5.5 $0.00014 $0.00279
Sonnet 5.5 $0.00007 $0.00139
Haiku 4.5 $0.00003 $0.00070

Measured 17d ago against content hash 4bbedc84e2c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

studio-security-auth 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 17d 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.

.agents/skills/studio-security-auth/SKILL.md · 73 lines

How it starts

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

Studio Security Auth

Use This Skill When

  • The task changes or reviews API-key validation.
  • The task changes or reviews browser sessions, the session cookie, or the order of authentication layers.
  • The task changes or reviews internal authentication gRPC between the backend and ingestion.
  • The user asks for a security review of authentication-sensitive code.

Do Not Use This Skill When

  • The task is ordinary subsystem work with no authentication or security impact.
  • The task merely lives near authentication code without changing the trust boundary.

Surface To Inspect

  • apps/studio/backend/server/src/app.rs
  • apps/studio/backend/server/src/config.rs
  • apps/studio/backend/server/src/features/auth/
  • apps/studio/backend/server/src/features/evaluation_tokens/ (developer access tokens and the bearer authorizer in access.rs)
  • apps/studio/backend/server/src/features/cli_sign_in/ (the CLI's browser sign-in: two public routes and three session routes)
  • apps/studio/backend/server/src/features/internal_auth.rs
  • apps/studio/ingestion/src/server/auth.rs
  • apps/studio/ingestion/src/backend/client.rs
  • apps/studio/proto/auth.proto
  • tooling/scripts/provision_local_studio.py
  • tooling/scripts/validate_agent_studio_e2e.py

Workflow

  1. Read apps/studio/AGENTS.md and apps/studio/docs/adr/012-studio-authentication.md, which owns the credential families and the session decisions. Studio ADR-009 owns ingestion API-key validation.
  2. Trace the full trust boundary: caller, credential transport, cache, layer or extractor, backend validation, and failure mode.
  3. Verify fail-closed behavior where it matters.
  4. Prefer concrete threat-model checks over generic security filler.
  5. Inspect active configuration and layers when deployment rules matter.
  6. Pair with studio-backend-rust or studio-ingestion-flow when the change crosses those subsystem boundaries.
  7. Local E2E users are explicit setup-API actions, never runtime or schema seeds. apps/studio/TESTING.md owns reset and validation procedures.
  8. For repository-local stack setup, persistent development credentials, or example environment preparation, use junjo-local-development and its owning runbook.

Read the full file on GitHub · 73 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. 17d ago Changed · +10 lines · -3 tokens per session 4bbedc84e2c0
  2. 1mo ago First seen · 63 lines · 38 tokens per session scan A c3941ebe9921

Subscribe to this mod's changes

studio-security-auth is a skill published in the GitHub repository mdrideout/junjo (20 stars, last pushed 17d ago), licensed Apache-2.0. It adds 35 tokens to every session and 697 once invoked, about $0.0001 per session on Opus 5.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.