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-docs-syncnpx skills add mdrideout/junjo --skill studio-docs-syncgit 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.00032 | $0.00393 |
| Opus 5 | $0.00016 | $0.00197 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
studio-docs-sync 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 2d 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 Docs Sync
Use This Skill When
- The task reviews Studio documentation or skills for drift.
- The task updates Studio documentation after implementation changes.
- The task rationalizes ownership among ADRs, agent guidance, READMEs, and near-code documentation.
Ownership
- Code and tests own implementation behavior.
- ADRs own decisions, reasoning, and consequences.
AGENTS.mdfiles provide concise runtime routing and mandatory constraints.- Skills provide task workflow and point to owners; they are not parallel architecture manuals.
- READMEs provide human onboarding and links to deeper owners.
Workflow
- Inventory the active owners before drawing conclusions:
- root and scoped
AGENTS.mdfiles - repo-local skills under
.agents/skills/ - Studio ADRs under
apps/studio/docs/adr/andapps/studio/ingestion/adr/ - near-code docs such as
apps/studio/TESTING.mdandapps/studio/backend/app/db_sqlite/README.md
- root and scoped
- Start from current code and tests.
- Check for stale file references, contradictory decisions, duplicated sources of truth, runtime defaults copied into prose, and implementation details in the wrong document.
- Report first when the request is an audit.
- When editing, update the owning document and use links elsewhere. Do not patch the same explanation into several files.
Validation
- Re-read changed docs and skills for duplication and contradictions.
- Verify every referenced path and command against the repository.
- Verify that linked ADRs still exist and own the stated decision.
- Keep Studio ADRs decision-level and skills workflow-level.
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.
- 2d ago First seen · 47 lines · 32 tokens per session scan A 771849cc5574
studio-docs-sync is a skill published in the GitHub repository mdrideout/junjo (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 32 tokens to every session and 393 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.