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/jedmamosto/open-agent-engine/agents-mdgit clone --depth 1 https://github.com/jedmamosto/open-agent-engineWrote 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/jedmamosto/open-agent-engine/agents-md)<a href="https://agentmods.dev/instructions/jedmamosto/open-agent-engine/agents-md"><img src="https://agentmods.dev/badge/instructions/jedmamosto/open-agent-engine/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.00454 | $0.00454 |
| Opus 5 | $0.00227 | $0.00227 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
open-agent-engine 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 3d 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.
What it actually says
Agent Directives: open-agent-engine
Cross-platform multi-agent scaffolding, skill package manager, and transpiler engine
1. Context Routing Index
- Active Sprint & Backlog: inspect agent_docs/backlog.md
- Product & Scope: inspect PRODUCT.md
- Design & Visual Identity: inspect DESIGN.md
- Architecture & Compilers: inspect agent_docs/architecture.md
- Workflow & Educational Concepts: inspect agent_docs/workflow_and_concepts.md
- Beginner's ELI5 Guide: inspect agent_docs/beginners_guide.md
- Subagents Directory: inspect .agents/personas/
2. Environment & Shell Commands
Execute in shell with strict sequential separators:
- Install:
pnpm install - Build:
pnpm build - Test:
pnpm test - Typecheck:
pnpm typecheck - Dev Mode:
pnpm dev
3. Operational Invariants & Boundaries ("Rule + Why")
A. ALWAYS Do
- Validate All Manifests Against Zod Schemas
- Why: Catch malformed user configuration early before transpilation to downstream IDEs.
- Preserve Progressive Disclosure
- Why: Keep root instruction files under 150 lines to prevent prompt cache invalidations.
- Verify All Tests Pass Before PR
- Why: Prevent broken regressions across adapter pipelines.
- Submit Changes via Branch PR with Approval
- Why:
mainbranch is protected by GitHub Repository Rulesets to prevent unvetted code changes.
- Why:
B. NEVER Do
- Never Write Platform-Specific Logic in Core Schemas
- Why: Maintain 100% vendor-neutral canonical AST representations.
- Never Emit Malformed Frontmatter
- Why: Target IDE parsers fail unpredictably when encountering broken YAML headers.
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.
- 3d ago First seen · 39 lines · 454 tokens per session scan A e0c7054c9cdf
open-agent-engine AGENTS.md is an instructions file published in the GitHub repository jedmamosto/open-agent-engine (4 stars, last pushed 14d ago), licensed MIT. It adds 454 tokens to every session, about $0.0023 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.