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.
curl -O https://raw.githubusercontent.com/mdrideout/junjo/master/.agents/skills/junjo-local-development/SKILL.mdgit 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/junjo-local-development)<a href="https://agentmods.dev/skills/mdrideout/junjo/junjo-local-development"><img src="https://agentmods.dev/badge/skills/mdrideout/junjo/junjo-local-development/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.
<a href="https://agentmods.dev/skills/mdrideout/junjo/junjo-local-development"><img src="https://agentmods.dev/badge/skills/mdrideout/junjo/junjo-local-development.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00041 | $0.00354 |
| Opus 5.5 | $0.00016 | $0.00142 |
| Sonnet 5.5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
junjo-local-development 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.
What it actually says
Junjo Local Development
Owners
- Read
apps/studio/TESTING.mdfor the greenfield reset, local identity, credential provisioning, and validation workflow. - Read the selected example's README and
.env.examplefor its runtime and configuration contract. - Use
tooling/scripts/provision_local_studio.pyto prepare persistent local Studio credentials and ignored example environments.
Required boundaries
- Create the local owner and credentials only through Studio's public setup, session, and management APIs.
- Never edit SQLite, add schema or startup seeds, commit generated
credentials, or copy local
.envfiles into deployment artifacts. - Use persistent provisioned credentials for local human or coding-agent iteration. Keep automated validators isolated with disposable credentials that they create and remove themselves.
- Treat
apps/studio/TESTING.mdand the example-owned files as sources of truth. Do not reproduce their endpoint, credential, or environment details in new agent guidance.
Workflow
- Identify whether the task needs an ordinary restart or an explicitly authorized greenfield reset.
- Follow the Studio testing runbook to configure and start the development stack.
- Run the local provisioner before starting examples or evaluation commands.
- Follow the selected example's own run and validation instructions.
- Keep production deployment work in its owning deployment workflow; the local provisioner must never be used against production or a remote Studio.
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.
- 17d ago Changed e9d96ad09c56
- 1mo ago First seen · 40 lines · 41 tokens per session scan A 50b9a253200d
junjo-local-development is a skill published in the GitHub repository mdrideout/junjo (20 stars, last pushed 17d ago), licensed Apache-2.0. It adds 41 tokens to every session and 354 once invoked, about $0.0002 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.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
storybook-testing
Storybook 10 testing patterns with Vitest integration, ESM-only distribution, CSF3 typesafe factories, play() interaction tests, Chromatic TurboSnap visual regression, module automocking, accessibility addon testing, and autodocs generation. Use when writing component stories, setting up visual regression testing…