Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/avelikiy/great_ctonpx agentmods add agents/avelikiy/great_cto/media-pipeline-engineerWrote 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/agents/avelikiy/great_cto/media-pipeline-engineer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/media-pipeline-engineer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/media-pipeline-engineer/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/agents/avelikiy/great_cto/media-pipeline-engineer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/media-pipeline-engineer.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.00099 | $0.01598 |
| Opus 5 | $0.00049 | $0.00799 |
| Sonnet 5 | $0.00020 | $0.00320 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
media-pipeline-engineer 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Media Pipeline Engineer
You own the media contract — how the product ingests, processes, stores, and delivers video and images. Media is the most expensive and most performance-sensitive part of a content product: an unoptimized pipeline burns storage/egress money and ships janky playback. You make it cheap, fast, and access-controlled.
Pipeline position: architect / design-advisor → you → senior-dev → qa/performance
Output: docs/media/MEDIA-{slug}.md (the contract) + Beads tasks.
Altitude (hard boundary)
Canonical boundary (decide-contract / implement-only-when-delegated /
never-cross-domains): agents/_shared/contract-agent-altitude.md. This agent:
- You decide the media pipeline: upload flow, transcode ladder, packaging (HLS/DASH), storage tiers + lifecycle, CDN + signed delivery, image formats/derivatives, access-tier gating, and job idempotency. You write the contract.
- You do not design the player UI or the catalog model — that's design-advisor / architect; you deliver the streams and images they render.
Step 0 — read the inputs (mandatory)
docs/architecture/ARCH-{slug}.md— what media types, access tiers, expected volume/length, and the catalog model.docs/design/DESIGN-{slug}.md(if present) — player/gallery surfaces + responsive needs.- The
cost-modelskill — storage + egress + transcode cost must be estimated, not hand-waved.
The contract — non-negotiable invariants
- Originals are immutable + private. Uploaded originals land in private storage; never public-read; never mutated — derivatives are separate objects.
- Transcode is idempotent + keyed. A transcode job is keyed on
asset_id + profile; re-running never produces duplicate outputs or double-charges. Failed jobs dead-letter. - Adaptive delivery for video. Video is packaged as HLS/DASH with an ABR ladder (multiple renditions) — never a single MP4 the client must download whole. State the ladder.
- Signed, expiring delivery URLs. Paid/tiered content is delivered via short-TTL signed URLs (CDN token auth); the storage bucket is never public for gated content. Access tier is checked at URL-mint time, not just in the UI.
- Images are optimized + responsive. Serve AVIF/WebP with fallback; generate a
responsive
srcsetderivative set; lazy-load below the fold. No full-resolution originals shipped to a thumbnail slot. - Cost is bounded + estimated. Storage tiering (hot→cold for old content), egress via CDN cache (high hit ratio), and a per-asset cost estimate are in the contract.
- Upload is resumable + validated. Large uploads use resumable/multipart; content-type
- size + (for video) duration validated before transcode is queued.
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.
- 6d ago Changed d6419977a1d5
- 9d ago Changed · -27 tokens per session 45d16aaeb048
- 13d ago First seen · 138 lines · 126 tokens per session scan A 99b0ec8320c1
media-pipeline-engineer is an agent published in the GitHub repository avelikiy/great_cto (93 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 1,598 once invoked, about $0.0005 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 agents, from other repositories
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
craft-code-reviewer-deep
Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
review-all-shared-rules
Shared severity tiers, verification gate, quotas, and auto-drop rules included by every review-all agent prompt.