MediaGo is a cross-platform application for finding and downloading online video streams, including m3u8/HLS media and videos from services such as YouTube and Bilibili. It is for people and automated tools that need to save videos through a desktop app, Docker, browser extension, or HTTP API. The catalogue entries let coding agents operate MediaGo to create downloads and check their progress.
Borrowing it
Nothing to install: this file belongs to mediago-dev/mediago. 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/mediago-dev/mediago/master/AGENTS.mdgit clone --depth 1 https://github.com/mediago-dev/mediagoWrote 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/instructions/mediago-dev/mediago/agents-md)<a href="https://agentmods.dev/instructions/mediago-dev/mediago/agents-md"><img src="https://agentmods.dev/badge/instructions/mediago-dev/mediago/agents-md/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/instructions/mediago-dev/mediago/agents-md"><img src="https://agentmods.dev/badge/instructions/mediago-dev/mediago/agents-md.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.01138 | $0.01138 |
| Opus 5.5 | $0.00455 | $0.00455 |
| Sonnet 5.5 | $0.00228 | $0.00228 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
mediago AGENTS.md 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 today.
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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
MediaGo is a pnpm/turborepo monorepo registered in one.manifest.toml. Feature apps live in apps/ (core for the Go backend, electron for desktop, ui for the shared frontend, player-ui for playback). Reusable logic stays in packages/, including common, core-sdk, electron-preload, and tooling. Long-form docs and assets sit in docs/, images/, and docker/. End-to-end checks live in tests/.
Tooling and Script Placement
Repository automation is centralized in packages/tooling.
- Do not create app-local or package-local
scripts/directories. - Put build, development, release, migration, code-generation, and verification entrypoints under
packages/tooling/src/<domain>/and invoke them fromTaskfile.ymlor package scripts. - Before adding a new tooling entrypoint, search
packages/toolingand extend an existing domain module when practical. - Keep product runtime code in its owning app or package; this rule applies to repository automation and one-off executable tooling, not application features.
Documentation Site Safety
docs/ is the production VitePress source directory. Its contents are packaged and deployed to the public documentation site.
- Never create agent planning or working artifacts anywhere under
docs/. This includesdocs/plans/,docs/superpowers/, design or implementation plans, audit reports, task logs, handoff notes, scratch Markdown, generated prompts, and session notes. - Only add or edit files under
docs/when they are intentional public documentation, documentation assets, VitePress source/configuration, or tests required for the documentation site. - Store persistent internal planning artifacts under
.agents/plans/. Store disposable artifacts in the system temporary directory. - This rule overrides any skill, tool, or template that defaults to writing plans under
docs/ordocs/plans/. - Before finishing a task that touches documentation, inspect
git status --short -- docsand remove accidental internal artifacts without deleting legitimate documentation content.
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.
- today Changed · +101 tokens per session 71ecbc43b38d
- 1mo ago First seen · 58 lines · 1,037 tokens per session scan A 238ed4d52f18
mediago AGENTS.md is an instructions file published in the GitHub repository mediago-dev/mediago (9,275 stars, last pushed today), licensed MIT. It adds 1,138 tokens to every session, about $0.0046 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.