junjo: Skill for Claude Code

.agents/skills/studio-docs-sync/SKILL.md

studio-docs-sync is a skill for Claude Code, Codex from mdrideout/junjo. It costs 32 tokens per session (389 once invoked), scanned A, original, Apache-2.0.

A documentation-review workflow for Junjo AI Studio projects. It checks whether documentation and local coding-agent skills still match the code and tests.

In plain words
What is it for?
Use it to audit Studio docs and skills, clean up outdated architecture decision records, and decide which document should own each piece of information.
Why use it?
It helps prevent stale file links, conflicting instructions, and duplicated or misplaced explanations after implementation changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is mdrideout/junjo's own configuration. It tells Claude Code and Codex how to work on junjo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything junjo configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/mdrideout/junjo/master/.agents/skills/studio-docs-sync/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mdrideout/junjo

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for studio-docs-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/mdrideout/junjo/studio-docs-sync/github.svg)](https://agentmods.dev/skills/mdrideout/junjo/studio-docs-sync)
Your own site
<a href="https://agentmods.dev/skills/mdrideout/junjo/studio-docs-sync"><img src="https://agentmods.dev/badge/skills/mdrideout/junjo/studio-docs-sync/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.

agentmods 80×15 button for studio-docs-sync

Your own site · 80×15
<a href="https://agentmods.dev/skills/mdrideout/junjo/studio-docs-sync"><img src="https://agentmods.dev/badge/skills/mdrideout/junjo/studio-docs-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 389 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00389
Opus 5.5 $0.00013 $0.00156
Sonnet 5.5 $0.00006 $0.00078
Haiku 4.5 $0.00003 $0.00039

Measured 17d ago against content hash 9776e81a3a06, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.agents/skills/studio-docs-sync/SKILL.md · 47 lines

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.md files 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

  1. Inventory the active owners before drawing conclusions:
    • root and scoped AGENTS.md files
    • repo-local skills under .agents/skills/
    • Studio ADRs under apps/studio/docs/adr/ and apps/studio/ingestion/adr/
    • near-code docs such as apps/studio/TESTING.md and apps/studio/backend/README.md
  2. Start from current code and tests.
  3. Check for stale file references, contradictory decisions, duplicated sources of truth, runtime defaults copied into prose, and implementation details in the wrong document.
  4. Report first when the request is an audit.
  5. 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.
Changes

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.

  1. 17d ago Changed 9776e81a3a06
  2. 1mo ago First seen · 47 lines · 32 tokens per session scan A 771849cc5574

Subscribe to this mod's changes

studio-docs-sync is a skill published in the GitHub repository mdrideout/junjo (20 stars, last pushed 17d ago), licensed Apache-2.0. It adds 32 tokens to every session and 389 once invoked, about $0.0001 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.