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/microrepar/awesome-opencode-agents/agents-mdgit clone --depth 1 https://github.com/microrepar/awesome-opencode-agentsWhat 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.03164 | $0.03164 |
| Opus 5 | $0.01582 | $0.01582 |
| Sonnet 5 | $0.00633 | $0.00633 |
| Haiku 4.5 | $0.00316 | $0.00316 |
Grade A, and why
awesome-opencode-agents 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 2d 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to OpenCode when working with code in this repository.
Project Overview
This is the Awesome OpenCode Agents repository - a collection of 24 specialized AI agents that extend OpenCode's capabilities through intelligent orchestration and domain expertise. The agents work together as a development team, with each agent having specific expertise and delegation patterns.
Dev Environment Tips
- Install dependencies with
npm installbefore running scaffolds. - Use
npm run devfor the interactive TypeScript session that powers local experimentation. - Run
npm run buildto refresh the CommonJS bundle indist/before shipping changes. - Store generated artefacts in
.context/so reruns stay deterministic.
Testing Instructions
- Execute
npm run testto run the Jest suite. - Append
-- --watchwhile iterating on a failing spec. - Trigger
npm run build && npm run testbefore opening a PR to mimic CI. - Add or update tests alongside any generator or CLI changes.
PR Instructions
- Follow Conventional Commits (for example,
feat(scaffolding): add doc links). - Cross-link new scaffolds in
docs/README.mdandagents/README.mdso future agents can find them. - Attach sample CLI output or generated markdown when behaviour shifts.
- Confirm the built artefacts in
dist/match the new source changes.
Working with Agents
When creating or modifying agents:
- Agents are Markdown files with YAML frontmatter (for agent definitions)
- Most agents should omit the
toolsfield to inherit all available tools - Use XML-style examples in descriptions for intelligent invocation
- Agents return structured findings for main agent coordination
Orchestration Pattern for OpenCode
Since sub-agents in OpenCode cannot directly invoke other sub-agents, orchestration follows this strict pattern:
CRITICAL: Agent Routing Protocol
When handling complex tasks, you MUST:
- ALWAYS start with tech-lead-orchestrator for any multi-step task
- FOLLOW the agent routing map returned by tech-lead EXACTLY
- USE ONLY the agents explicitly recommended by tech-lead
- NEVER select agents independently - tech-lead knows which agents exist
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.
- 2d ago First seen · 375 lines · 3,164 tokens per session scan A ccbe6a546acf
awesome-opencode-agents AGENTS.md is an instructions file published in the GitHub repository microrepar/awesome-opencode-agents (1 stars, last pushed 6mo ago), licensed MIT. It adds 3,164 tokens to every session, about $0.0158 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
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).
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.
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.