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/memex-lab/dart_agent_core/agents-mdgit clone --depth 1 https://github.com/memex-lab/dart_agent_coreWrote 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/memex-lab/dart_agent_core/agents-md)<a href="https://agentmods.dev/instructions/memex-lab/dart_agent_core/agents-md"><img src="https://agentmods.dev/badge/instructions/memex-lab/dart_agent_core/agents-md.svg" alt="Measured on agentmods" 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 | $0.01450 | $0.01450 |
| Opus 5 | $0.00725 | $0.00725 |
| Sonnet 5 | $0.00290 | $0.00290 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
dart_agent_core 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 4d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Qoder (qoder.com) when working with code in this repository.
dart_agent_core is a mobile-first / local-first Dart library that implements a full agentic loop (tool use, streaming, state persistence, skills, sub-agents, planning, context compression, loop detection) plus an agent-evaluation subsystem. It targets Flutter/Dart apps with no Python or Node.js backend, and supports all 6 platforms including Web.
Common Commands
dart pub get # install dependencies
dart analyze . # static analysis (whole package, matches pana/CI)
dart format . # format; pana fails the score if anything is unformatted
dart test # run all tests
dart test test/planner_test.dart # run a single test file
dart test -n "substring" # run tests whose name matches
# Regenerate mockito mocks (*.mocks.dart) after changing mocked classes
dart run build_runner build --delete-conflicting-outputs
# Pub-score / platform-tag review (web support, lints, formatting)
pana --no-warning .
Running examples and the eval demo (require provider credentials via env vars):
export OPENAI_API_KEY=sk-...
dart run example/simple_agent_example.dart
# Eval harness demo: --suite calculator|card_agent|pkm_agent|all, --mode live|record|replay
export OPENAI_BASE_URL=https://...
dart run example/eval_demo/main.dart --suite all --concurrency 4 --mode live
# Transcript viewer CLI (reads eval traces)
dart run bin/transcripts.dart
Two Public Libraries
The package exposes two separate entry points — keep them decoupled:
lib/dart_agent_core.dart— the agent runtime (clients, agent, tools, skills, state).lib/eval.dart— the evaluation subsystem (tasks, graders, suites, record/replay, metrics, reporting). It is intentionally a separate import so apps that don't run evals don't pay the import cost. Do not pull eval primitives into the main library.
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.
- 4d ago First seen · 82 lines · 1,450 tokens per session scan A 8fbd13fefc46
dart_agent_core AGENTS.md is an instructions file published in the GitHub repository memex-lab/dart_agent_core (42 stars, last pushed 6d ago), licensed MIT. It adds 1,450 tokens to every session, about $0.0072 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
fast-agent AGENTS.md
AGENTS.md instructions for evalstate/fast-agent, covering fast-agent contributor notes and architectural orientation.
kungfu CLAUDE.md
Claude Code instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before working in this repository. It routes both product use and contribution work to the repository sources of truth, including the requirement that development and build tasks enter through Shifu.
kungfu copilot-instructions.md
Copilot instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before proposing or running changes. It is the shared agent router for this repository, including the canonical Shifu development and build entrypoint.
yoagent CLAUDE.md
Instructions for yologdev/yoagent, covering claude.md, project overview, build & development commands, architecture and core loop pattern.
wind dynamic.instructions.md
Instructions for fluttersdk/wind, covering dynamic json renderer (lib/src/dynamic/), json schema, security model (whitelist first), state binding (id-keyed widgets) and action dispatch.
wind docs.instructions.md
Instructions for fluttersdk/wind, covering documentation conventions (doc/), file shape (every doc file), wfoo, basic usage and props.