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 agentmods add skills/mdrideout/junjo/studio-security-authnpx skills add mdrideout/junjo --skill studio-security-authgit clone --depth 1 https://github.com/mdrideout/junjoWrote 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/mdrideout/junjo/studio-security-auth)<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="Measured on agentmods" height="20"></a>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 | $0.00038 | $0.00549 |
| Opus 5 | $0.00019 | $0.00275 |
| Sonnet 5 | $0.00008 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 63 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 session cookies, CORS, domain requirements, or authentication middleware ordering.
- 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/app/main.pyapps/studio/backend/app/config/settings.pyapps/studio/backend/app/features/auth/apps/studio/backend/app/features/internal_auth/apps/studio/ingestion/src/server/auth.rsapps/studio/ingestion/src/backend/client.rsapps/studio/proto/auth.prototooling/scripts/provision_local_studio.pytooling/scripts/validate_agent_studio_e2e.py
Workflow
- Read
apps/studio/AGENTS.md. There is no dedicated authentication ADR, so start from current code and tests. - Trace the full trust boundary: caller, credential transport, cache or middleware, backend validation, and failure mode.
- Verify fail-closed behavior where it matters.
- Prefer concrete threat-model checks over generic security filler.
- Inspect active settings and middleware when deployment rules matter.
- Pair with
studio-backend-pythonorstudio-ingestion-flowwhen the change crosses those subsystem boundaries. - Local E2E users are explicit setup-API actions, never runtime or migration
seeds.
apps/studio/TESTING.mdowns reset and validation procedures. - For repository-local stack setup, persistent development credentials, or
example environment preparation, use
junjo-local-developmentand its owning runbook.
Validation
- Run the smallest relevant backend or integration tests.
- Prioritize
apps/studio/backend/tests/security/,apps/studio/backend/tests/test_production_settings.py, andapps/studio/backend/app/features/internal_auth/test_*.py. - Validate both backend and ingestion when behavior crosses that boundary.
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.
- 3d ago First seen · 63 lines · 38 tokens per session scan A c3941ebe9921
studio-security-auth is a skill published in the GitHub repository mdrideout/junjo (20 stars, last pushed 4d ago), licensed Apache-2.0. It adds 38 tokens to every session and 549 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
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
dagr-producer
Emit and maintain a dagr run file — a live, contract-valid JSON description of recursive projects, tasks, attempts, gates, evidence, policies, events, and operator-message resolutions that dagr view renders as a DAG. Use when orchestrating agents or tracking multi-step work that a dagr pane should display.
diataxis-docs-writer
Write or improve software documentation using the Diátaxis framework — four documentation types (tutorials, how-to guides, reference, explanation), each serving a different user need. Use it whenever you're about to write or revise documentation for a finished feature, implementation, API, library, CLI, service, or…
opensource-guide-coach
Use when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding, community health, maintainer burnout, code of conduct, metrics, legal basics, or open source project adoption.
pytest-coverage
Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%.
nika-authoring
Author, check and repair Nika workflows (.nika.yaml files — the workflow language for AI). Use when writing or editing a .nika.yaml file, converting a repeated AI task or prompt chain into a workflow, or when nika check reports NIKA-XXXX findings to fix.