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/fredabila/orcbot/agents-mdgit clone --depth 1 https://github.com/fredabila/orcbotWhat 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.00813 | $0.00813 |
| Opus 5 | $0.00407 | $0.00407 |
| Sonnet 5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
orcbot 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to WARP (warp.dev) when working with code in this repository.
Common commands
- Install deps:
npm install - Build (tsc):
npm run build - Fast build:
npm run build:fast - Dev CLI (ts-node):
npm run dev - Run built CLI:
npm run start(runsdist/cli/index.js) - Tests (Vitest):
npm test - Watch tests:
npm run test:watch - Run a single test file:
npx vitest run tests/<file>.test.ts - Run a single test by name:
npx vitest run -t "test name" - Browser tooling smoke test:
npm run browser:test - Lint: no lint script is defined in
package.json
High-level architecture (big picture)
- CLI entrypoint:
src/cli/index.tswires the TUI, CLI commands, and bootstraps subsystems. - Agent core loop:
src/core/Agent.tsorchestrates the action loop (simulate → decide → execute tools → memory → termination review). - Decision stack:
src/core/DecisionEngine.tsbuilds prompts and calls the LLM.src/core/ParserLayer.tsnormalizes LLM output to structured JSON with fallbacks.src/core/DecisionPipeline.tsapplies guardrails on tool calls (dedup, loop detection, safety checks). Guardrails are intentional—avoid weakening them.src/core/SimulationEngine.tscreates a pre-plan before execution starts.src/core/prompts/contains modular helpers activated byPromptRouter.
- Memory system (critical):
src/memory/MemoryManager.tshandles short/episodic/long memory and consolidation.src/memory/ActionQueue.tsis the durable priority queue for tasks (retry, TTL, chaining).- Storage is file-backed via
src/storage/JSONAdapter.ts(atomic writes + backups). - Vector memory (
src/memory/VectorMemory.ts) is optional and file-backed. - Important constraints from existing instructions: keep
saveMemorycontent short (<500 chars), include metadata (actionId,step,skill) for step memories, and avoid storing secrets in memory.
- Skills system:
- Core skills registered in
src/core/Agent.ts. - Dynamic plugins loaded by
src/core/SkillsManager.tsfrom~/.orcbot/plugins/(or./plugins).
- Core skills registered in
- Channels:
src/channels/implements Telegram (Telegraf), WhatsApp (Baileys), Discord (discord.js), and Gateway (Express+WS). Inbound messages write short memory and push tasks to the queue. - Web/browser tooling:
src/tools/WebBrowser.tswraps Playwright and provides search fallbacks (Serper → Google → Bing → DuckDuckGo). - Config + runtime tuning:
src/config/ConfigManager.tsloadsorcbot.config.yamlwith hot-reload and feature toggles.src/core/RuntimeTuner.tsadjusts runtime limits based on signals.src/core/MultiLLM.tsroutes providers by model prefix and falls back on errors.
- Data paths: runtime state lives under
~/.orcbot/(orORCBOT_DATA_DIR) including config, memory, queue, logs, profiles, and plugins.
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 · 47 lines · 813 tokens per session scan A 52dd99d344ce
orcbot AGENTS.md is an instructions file published in the GitHub repository fredabila/orcbot (11 stars, last pushed 5mo ago), licensed MIT. It adds 813 tokens to every session, about $0.0041 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
xi AGENTS.md
AGENTS.md instructions for MairwunNx/xi: Communicate with user in preferly in russian language, but you can thinking in american english. For chatting you can use emoji.
workflow AGENTS.md
AGENTS.md instructions for vercel/workflow, covering agent instructions, architecture, core components, workflow execution model and development commands.
AstrBot copilot-instructions.md
Copilot instructions for AstrBotDevs/AstrBot, covering astrbot development instructions, working effectively, bootstrap and install dependencies, running the application and dashboard build (vue.js/node.js).
aghub AGENTS.md
Instructions for AkaraChen/aghub, covering aghub knowledge base, structure, where to look, conventions and rust.
openclaw CLAUDE.md
Claude Code instructions for openclaw/openclaw, a project described as: Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞.
OwnPilot AGENTS.md
Instructions for ownpilot/OwnPilot, covering ownpilot, architecture, key patterns, commands and tech stack.