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/bytedance/deer-flow/copilot-instructionsgit clone --depth 1 https://github.com/bytedance/deer-flowWhat 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.01714 | $0.01714 |
| Opus 5 | $0.00857 | $0.00857 |
| Sonnet 5 | $0.00343 | $0.00343 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
deer-flow copilot-instructions.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.
Copies of this mod
4 near-identical copies found in the catalogue:
- semantic-deer-flow copilot-instructions.md — 100% identical, 0 lines differ
- omniHarness copilot-instructions.md — 91% identical, 18 lines differ
- deer-flow-by-cc copilot-instructions.md — 89% identical, 4 lines differ
- deerflow2.0-enhanced copilot-instructions.md — 89% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Onboarding Instructions for DeerFlow
Use this file as the default operating guide for this repository. Follow it first, and only search the codebase when this file is incomplete or incorrect.
1) Repository Summary
DeerFlow is a full-stack "super agent harness".
- Backend: Python 3.12, LangGraph + FastAPI gateway, sandbox/tool system, memory, MCP integration.
- Frontend: Next.js 16 + React 19 + TypeScript + pnpm.
- Local dev entrypoint: root
Makefilestarts backend + frontend + nginx onhttp://localhost:2026. - Docker dev entrypoint:
make docker-*(mode-aware provisioner startup fromconfig.yaml).
Current repo footprint is medium-large (backend service, frontend app, docker stack, skills library, docs).
2) Runtime and Toolchain Requirements
Validated in this repo on macOS:
- Node.js
>=22(validated with Node23.11.0) - pnpm (repo expects lockfile generated by pnpm 10; validated with pnpm
10.26.2and10.15.0) - Python
>=3.12(CI uses3.12) uv(validated with0.7.20)nginx(required formake devunified local endpoint)
Always run from repo root unless a command explicitly says otherwise.
3) Build/Test/Lint/Run - Verified Command Sequences
These were executed and validated in this repository.
A. Bootstrap and install
- Check prerequisites:
make check
Observed: passes when required tools are installed.
- Install dependencies (recommended order: backend then frontend, as implemented by
make install):
make install
B. Backend CI-equivalent validation
Run from backend/:
make lint
make test
Validated results:
make lint: pass (ruff check .)make test: pass (277 passed, 15 warnings in ~76.6s)
CI parity:
.github/workflows/backend-unit-tests.ymlruns on pull requests.- CI executes
uv sync --group dev, thenmake lint, thenmake testinbackend/.
C. Frontend validation
Run from frontend/.
Recommended reliable sequence:
pnpm lint
pnpm typecheck
BETTER_AUTH_SECRET=local-dev-secret pnpm build
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 · 214 lines · 1,714 tokens per session scan A c0f1dabcd26d
deer-flow copilot-instructions.md is an instructions file published in the GitHub repository bytedance/deer-flow (81,129 stars, last pushed yesterday), licensed MIT. It adds 1,714 tokens to every session, about $0.0086 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
nexent AGENTS.md
Instructions for ModelEngine-Group/nexent, covering agents, available skills, project overview, developer commands and backend (python 3.11).
agents-universe CLAUDE.md
Instructions for agents-universe/agents-universe, covering agents universe — enterprise ai agent framework, project overview, monorepo layout, development commands and api (from packages/api/).
agent-graph AGENTS.md
AGENTS.md instructions for keta1930/agent-graph, covering commands, architecture, git conventions and test and format infrastructure.
agenticloop AGENTS.md
Instructions for bartoszarendt/agenticloop, covering agents.md, agentic loop is the subject here, not the process, purpose, source of truth and optional private project context.
earnings-edge copilot-instructions.md
Copilot instructions for suhaas/earnings-edge, covering earnings-edge: agent development guidelines, architecture & core concepts, the graph, agent roles and tools & skills boundary.
earnings-edge AGENTS.md
AGENTS.md instructions for suhaas/earnings-edge, covering earnings-edge: agent development guidelines, architecture & core concepts, the graph, agent roles and tools & skills boundary.