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/daisybastioned440/lite-research-agents/agents-mdgit clone --depth 1 https://github.com/Daisybastioned440/lite-research-agentsWrote 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/daisybastioned440/lite-research-agents/agents-md)<a href="https://agentmods.dev/instructions/daisybastioned440/lite-research-agents/agents-md"><img src="https://agentmods.dev/badge/instructions/daisybastioned440/lite-research-agents/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.00346 | $0.00346 |
| Opus 5 | $0.00173 | $0.00173 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
lite-research-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 5d 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.
This is a copy
100% identical to lite-research-agents AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Codex CLI — Research Agent Boot Contract
You are a research agent operating inside this repository. This file is your entry point.
On Startup
- Read
AGENT.md— your full operating instructions. Follow them without exception. - Read
skills/SKILLS.md— the registry of all available skills. These are your tools. - Determine the active project:
- If the user specifies a project folder (e.g.
projects/my-idea/), read<project>/PROJECT.md. - If a project folder is already open in the IDE, read its
PROJECT.md.
- If the user specifies a project folder (e.g.
- Follow the Bootstrap Sequence in
AGENT.md(fresh vs. resume).
Sandbox Rule
You may only read from or write to files within the active project's sandbox_root. Default is the project folder itself. This rule cannot be overridden.
Invoking Skills
Skills are not pre-loaded. Read skills/SKILLS.md to see what is available. Invoke a skill by reading its SKILL.md file — the content enters your context and you follow the instructions inside.
For type: tool skills, run the entry_point script via shell.
For type: agentic skills, you do not have a subagent spawning tool — follow the Single-Agent Fallback section in the skill's SKILL.md instead.
No Subagent Spawning
Codex runs as a single agent. When a skill playbook calls for spawning persona subagents, simulate each persona inline: prefix your response with the persona name and follow the persona definition strictly. Persona context isolation is reduced but the structured debate loop still applies.
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.
- 5d ago First seen · 30 lines · 346 tokens per session scan A 38ddc031418e
lite-research-agents AGENTS.md is an instructions file published in the GitHub repository Daisybastioned440/lite-research-agents (2 stars, last pushed 2d ago), licensed MIT. It adds 346 tokens to every session, about $0.0017 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to lite-research-agents AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
do-it AGENTS.md
AGENTS.md instructions for tdwhere123/do-it, covering agents.md, file rules, repository, source of truth vs build artifacts and closed-set contracts.
opendigitalproductfactory AGENTS.md
AGENTS.md instructions for OpenDigitalProductFactory/opendigitalproductfactory, covering dpf — agent rulebook, 1. first principles, 2. project architecture, 3. branching, commits & prs and 4. verification — build gate (mandatory).
codex-acp-bridge AGENTS.md
AGENTS.md instructions for normahq/codex-acp-bridge, covering codex-acp-bridge — agents.md, development standards, quality gates (required), logging policy and bridge guardrails.
opendigitalproductfactory copilot-instructions.md
Copilot instructions for OpenDigitalProductFactory/opendigitalproductfactory: Read /AGENTS.md at the repo root before any work in this project. It is the canonical rulebook; tool-specific files in this repo are pointers to it.
pi CLAUDE.md
Instructions for share-skills/pi, covering 强制, 内部目标（不可写入公开文件）, 跑分规范 and eval 驱动优化规则.
codebadger AGENTS.md
AGENTS.md instructions for qcri/codebadger, covering codebadger agent guide, what this repository is, development workflow, cpg and worker rules and mcp/tool contracts.