junjo: Skill for Claude Code

.agents/skills/studio-ingestion-flow/SKILL.md

studio-ingestion-flow is a skill for Claude Code, Codex from mdrideout/junjo. It costs 41 tokens per session (457 once invoked), scanned A, original, Apache-2.0.

A project-specific guide for Junjo AI Studio's OTLP ingestion path. OTLP is a format and protocol for sending telemetry such as traces, metrics, and logs to a system for storage and analysis.

In plain words
What is it for?
Use it when changing or reviewing telemetry ingestion, segmented WAL behavior, Parquet files, hot snapshots, recent-to-cold data bridging, or related protocol contracts.
Why use it?
It helps keep changes consistent across the write-ahead log, file flushing, snapshots, backend queries, protocol definitions, and duplicate handling.

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-ingestion-flow/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-ingestion-flow

README.md
[![agentmods](https://agentmods.dev/badge/skills/mdrideout/junjo/studio-ingestion-flow.svg)](https://agentmods.dev/skills/mdrideout/junjo/studio-ingestion-flow)
Your own site
<a href="https://agentmods.dev/skills/mdrideout/junjo/studio-ingestion-flow"><img src="https://agentmods.dev/badge/skills/mdrideout/junjo/studio-ingestion-flow.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 457 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.00041 $0.00457
Opus 5 $0.00020 $0.00229
Sonnet 5 $0.00008 $0.00091
Haiku 4.5 $0.00004 $0.00046

Measured 7d ago against content hash 93bf7870600b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

studio-ingestion-flow 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 7d 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-ingestion-flow/SKILL.md · 49 lines

What it actually says

Studio Ingestion Flow

Use This Skill When

  • The task touches apps/studio/ingestion/.
  • The task changes WAL behavior, segmenting, flush triggers, hot snapshots, backpressure, or recent-cold file bridging.
  • The task changes apps/studio/proto/ contracts used by ingestion and the backend.
  • The task changes backend code that directly depends on ingestion query semantics.

Do Not Use This Skill When

  • The task is ordinary FastAPI feature or CRUD work.
  • The task is frontend UI or state-management work.
  • The task is primarily an authentication review with no ingestion-path changes.

Workflow

  1. Read apps/studio/AGENTS.md and start from the code path.
  2. Trace the relevant end-to-end path before editing: OTLP receive, WAL write, cold flush, hot snapshot, backend query registration, and deduplication or recent-cold bridging.
  3. Use ADRs for decisions and invariants:
    • apps/studio/ingestion/adr/001-segmented-wal-architecture.md
    • apps/studio/ingestion/adr/002-sqlite-metadata-index.md
    • apps/studio/docs/adr/004-events-json-contract.md when events JSON is involved
  4. Treat apps/studio/ingestion/src/config.rs and active backend code as the source of truth for runtime defaults and behavior.
  5. Update owning proto sources and regenerate outputs through repository commands; never edit generated files manually.

Validation

  • Run cargo test --locked from apps/studio/ingestion for ingestion work.
  • Run relevant backend tests when query behavior or proto contracts change.
  • Use ./run-all-proto-gen.sh from apps/studio when Python proto generation is required.
  • Verify that documentation describes durable decisions rather than a runtime implementation snapshot.
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. 7d ago First seen · 49 lines · 41 tokens per session scan A 93bf7870600b

Subscribe to this mod's changes

studio-ingestion-flow is a skill published in the GitHub repository mdrideout/junjo (20 stars, last pushed 7d ago), licensed Apache-2.0. It adds 41 tokens to every session and 457 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.

Related

Other skills, from other repositories

developing-genkit-tooling

Best practices for authoring Genkit tooling, including CLI commands and MCP server tools. Covers naming conventions, architectural patterns, and consistency guidelines.

genkit-ai/genkit · 35 tokens

architecture-decision-record

ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.

yonatangross/orchestkit · 38 tokens

zcfg

Integrate zcfg (Zero Dependency Configuration Utility) into Java applications. Use when adding configuration loading, reading properties files, setting up application configuration, or integrating zcfg into a Java project. Triggers on "zcfg", "add configuration", "load properties", "application configuration with…

AdamBien/airails · 75 tokens

data-structures

Implements custom JavaScript data structures: queues, deques, stacks, linked lists, cons lists, circular buffers, unrolled lists, tries, heaps, graphs, LRU caches, CRDTs, pools, structs. Use when building or choosing non-native collections, optimizing enqueue/dequeue, designing persistent lists, or when the user asks…

metarhia/metaskills · 84 tokens

bce

Generic, composable architecture rules for the Boundary-Control-Entity (BCE/ECB) pattern — business components, layer responsibilities, package structure, and cross-component relationships. Technology-neutral; meant to be composed with language- or framework-specific skills (e.g. microprofile-server, web-components…

AdamBien/airails · 151 tokens

microprofile-server

Architecture and coding rules for long-running Java MicroProfile / Jakarta EE server applications — BCE layering, business components (BC), JAX-RS resources, CDI, JSON-P, testing (unit/integration/system), and Maven project structure. Use when creating, generating, scaffolding, writing, or reviewing code, resources…

AdamBien/airails · 87 tokens