Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/mediago-dev/mediago/agents-mdgit clone --depth 1 https://github.com/mediago-dev/mediagoWhat 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 | $0.01037 | $0.01037 |
| Opus 5 | $0.00518 | $0.00518 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00104 | $0.00104 |
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 yesterday.
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. Feature apps live in apps/ (frontend-main, frontend-mobile, backend-web, backend-electron) for the user surfaces and API. Reusable logic stays in packages/ (shared for cross-runtime helpers, backend for orchestration, main for Electron packaging). 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.
- yesterday 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,196 stars, last pushed 3d ago), licensed MIT. It adds 1,037 tokens to every session, about $0.0052 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 instructions, from other repositories
zahori AGENTS.md
Instructions for josesepulvedapino/zahori, covering zahori: guide for coding agents, commands, design rules (do not break) and layout.
media-downloader AGENTS.md
Instructions for Knuckles-Team/media-downloader, covering agents.md, tech stack & architecture, architecture diagram, workflow diagram and commands (run these exactly).
media-downloader CLAUDE.md
Instructions for Knuckles-Team/media-downloader: Guidance for Claude Code (claude.ai/code) when working in this repository.
vscode tree-widgets.instructions.md
Use when asked to consume workbench tree widgets in VS Code.
vscode accessibility.instructions.md
Use when implementing accessibility features, ARIA labels, screen reader support, accessible help dialogs, or keybinding scoping for accessibility. Covers AccessibleContentProvider, CONTEXTACCESSIBILITYMODEENABLED, verbosity settings, and announcement patterns.
vscode writing-tests.instructions.md
VS Code test writing guidelines — unit tests, integration tests, snapshot tests, and clean teardown patterns. Reference when writing or updating tests.