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-api-contractsnpx skills add mdrideout/junjo --skill studio-api-contractsgit 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.00035 | $0.00311 |
| Opus 5 | $0.00017 | $0.00156 |
| Sonnet 5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
studio-api-contracts 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.
What it actually says
Studio API Contracts
Contract Decisions
- Backend routes and Pydantic schemas own REST contracts.
- Generated OpenAPI is a transport artifact, not a hand-edited source.
- Frontend Zod schemas and request code are consumers and change with the backend contract.
- Authentication, cookies, CORS, status codes, and error envelopes are part of the endpoint contract.
- A cross-boundary change is incomplete until the producer and every affected consumer are validated together.
Surface To Inspect
apps/studio/backend/app/features/and the owning backend testsapps/studio/backend/scripts/export_openapi_schema.pyapps/studio/frontend/backend/openapi.jsonapps/studio/frontend/src/features/orapps/studio/frontend/src/auth/apps/studio/frontend/src/__tests__/contracts/apps/studio/frontend/src/__tests__/integration/- SDK or CLI clients that call the same route
Routing
Use studio-backend-python for backend implementation,
studio-frontend-react for browser implementation, and
studio-security-auth when the contract includes credentials, sessions, or
CORS. Validation commands remain owned by scoped AGENTS.md files; concrete
behavior remains owned by code and tests.
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 · 36 lines · 35 tokens per session scan A f955f8f33522
studio-api-contracts is a skill published in the GitHub repository mdrideout/junjo (20 stars, last pushed 3d ago), licensed Apache-2.0. It adds 35 tokens to every session and 311 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.