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/studio-ingestion-flow/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/studio-ingestion-flow)<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>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.00457 |
| Opus 5 | $0.00020 | $0.00229 |
| Sonnet 5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
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.
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
- Read
apps/studio/AGENTS.mdand start from the code path. - 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.
- Use ADRs for decisions and invariants:
apps/studio/ingestion/adr/001-segmented-wal-architecture.mdapps/studio/ingestion/adr/002-sqlite-metadata-index.mdapps/studio/docs/adr/004-events-json-contract.mdwhen events JSON is involved
- Treat
apps/studio/ingestion/src/config.rsand active backend code as the source of truth for runtime defaults and behavior. - Update owning proto sources and regenerate outputs through repository commands; never edit generated files manually.
Validation
- Run
cargo test --lockedfromapps/studio/ingestionfor ingestion work. - Run relevant backend tests when query behavior or proto contracts change.
- Use
./run-all-proto-gen.shfromapps/studiowhen Python proto generation is required. - Verify that documentation describes durable decisions rather than a runtime implementation snapshot.
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.
- 7d ago First seen · 49 lines · 41 tokens per session scan A 93bf7870600b
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.
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.
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.
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…
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…
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…
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…