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-backend-pythonnpx skills add mdrideout/junjo --skill studio-backend-pythongit clone --depth 1 https://github.com/mdrideout/junjoWhat 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.00041 | $0.00552 |
| Opus 5 | $0.00020 | $0.00276 |
| Sonnet 5 | $0.00008 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
studio-backend-python 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Studio Backend Python
Use This Skill When
- The task touches
apps/studio/backend/app/,apps/studio/backend/migrations/, orapps/studio/backend/conftest.py. - The task changes FastAPI endpoints, Pydantic schemas, services, repositories, SQLite usage, DataFusion orchestration, or backend-visible ingestion query behavior.
- The task changes backend tests, scripts, or organization.
Do Not Use This Skill When
- The task is primarily ingestion runtime flow work.
- The task is primarily frontend UI or state work.
- The task is primarily an authentication review better handled by
studio-security-auth.
Workflow
- Read
apps/studio/AGENTS.md, then start from the touched code and nearest tests. - Use owner docs only where they constrain the work:
apps/studio/backend/app/db_sqlite/README.mdapps/studio/TESTING.mdapps/studio/ingestion/adr/002-sqlite-metadata-index.mdfor indexing and recent-cold bridge invariantsapps/studio/ingestion/adr/001-segmented-wal-architecture.mdfor hot snapshot or WAL semanticsapps/studio/docs/adr/004-events-json-contract.mdforevents_json
- Keep backend code explicit and single-purpose.
- Follow the scoped runtime rules: no legacy fallbacks and no hand-edited Alembic migrations.
- Pair with
studio-ingestion-flowwhen changing query bridging, proto contracts, or hot-snapshot behavior. - Pair with
studio-security-authwhen changing an authentication trust boundary, middleware order, cookie policy, or API-key validation. - Keep ADRs strategic and update the owning document only.
- Never access a running backend container's bind-mounted SQLite database or
WAL from a host process.
apps/studio/TESTING.mdowns the stopped-stack reset procedure.
Validation
Run the smallest relevant checks from apps/studio:
./backend/scripts/run-backend-tests.shcd backend && uv run ruff check app/./backend/scripts/validate_rest_api_contracts.shwhen REST contracts change
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.
- yesterday First seen · 58 lines · 41 tokens per session scan A 5b2106f116c7
studio-backend-python is a skill published in the GitHub repository mdrideout/junjo (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 552 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%.
writing-workspace-jobs
Author FSM workspace jobs. Use when creating, editing, or debugging jobs, signals, or FSM workflows in workspace.yml.