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/peacenode/livepeer-agent/agents-mdgit clone --depth 1 https://github.com/peacenode/livepeer-agentWhat 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.00249 | $0.00249 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
livepeer-agent 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.
What it actually says
Livepeer Agent contribution boundaries
Product boundaries
- Do not import application code, authentication implementations, generated output, credentials, sessions, or Git history from sibling or private repositories.
- Treat external reference applications as reference material only. Reimplement required behavior against this repository's documented contracts and dependency licenses.
- Livepeer MCP owns Livepeer identity, email verification, and access for each Daydream API key. Do not add a parallel product-auth or entitlement system.
- Never perform paid media calls from tests.
- Never commit
.envfiles, credentials, user email addresses, prompts, or session data.
Package ownership
apps/cli: command entrypoint, local credentials, agent and TUI surfaces.packages/contracts: frozen cross-package interfaces and test doubles. Contract changes require explicit review.packages/livepeer-client: transport-neutral MCP client and normalization.packages/model-providers: Pi model-provider catalog and resolution.
Keep changes within the owning package where possible. Make cross-package contract changes explicit and review them independently.
Quality gate
Run lint, typecheck, tests, build, and package validation before committing. Tests use fake credential and MCP providers unless a separate live smoke test is explicitly authorized.
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 · 23 lines · 249 tokens per session scan A 78b3558cb8a3
livepeer-agent AGENTS.md is an instructions file published in the GitHub repository peacenode/livepeer-agent (0 stars, last pushed 14d ago), licensed Apache-2.0. It adds 249 tokens to every session, about $0.0012 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-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.