What is lore-oss AGENTS.md?

Repository instructions for Lore, a project that uses a shared task pipeline to organize development work.

Checking available work, continuing a claimed task, starting a feature, and using the project's feature and pull-request commands.

They help a new developer understand the current task state and the required workflow before starting a feature.

How re-cinq/lore-oss configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to re-cinq/lore-oss. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/re-cinq/lore-oss/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/re-cinq/lore-oss

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/re-cinq/lore-oss/agents-md/github.svg)](https://agentmods.dev/instructions/re-cinq/lore-oss/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/re-cinq/lore-oss/agents-md"><img src="https://agentmods.dev/badge/instructions/re-cinq/lore-oss/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/re-cinq/lore-oss/agents-md"><img src="https://agentmods.dev/badge/instructions/re-cinq/lore-oss/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 932 This file is loaded in full into every session.

When invoked 932 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.1	$0.00932	$0.00932
Opus 5.5	$0.00373	$0.00373
Sonnet 5.5	$0.00186	$0.00186
Haiku 4.5	$0.00093	$0.00093

Measured 2mo ago against content hash 560126d6aec9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lore-oss 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 2mo 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.

AGENTS.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent instructions

First session (new developer)

If this looks like the developer's first session (no pipeline tasks, no recent git activity in this repo), say:

"Welcome to [repo name]. I have your team's context loaded — conventions, active decisions, and current work. A few things to know:

ready_tasks (MCP) shows what's available to work on
/lore-feature sets up a new feature end-to-end
/lore-pr drafts your PR description when you're done

Want me to show you what's currently unblocked?"

Orientation

At the start of every session, check pipeline task state via MCP:

If a task is claimed: tell the developer which task is in progress and offer to continue.
If no task is claimed: call ready_tasks to see unblocked tasks.
Never ask the developer to manually load context. MCP handles this.

Starting a feature

If the developer mentions starting a new feature, building something new, or picking up a ticket:

Suggest /lore-feature before they do anything else.
Do not ask them to run specify, lore-gen-constitution, or sync_tasks separately. /lore-feature handles all of it.

During implementation

All context (org conventions, team patterns, ADRs) is loaded via MCP.
All task state is tracked via pipeline MCP tools.
Do not ask the developer to provide context you already have.
If uncertain about a convention, check MCP via get_context before asking.

Finishing work

When the developer signals they are done with a piece of work:

Confirm the task should be marked done: call complete_task via MCP.
If the task had dependents, mention that they are now unblocked.

Opening a PR

If the developer mentions opening a PR, creating a pull request, or pushing for review:

Suggest /lore-pr before they open a browser.
Do not let them write the PR description from scratch if a spec exists.

Delegating work to the cluster

Use create_pipeline_task when:

A task will take more than ~20 minutes (long tests, ingestion, gap analysis)
The task is well-defined and does not need interactive decisions
You want to keep the local session focused on something else

Read the full file on GitHub · 117 lines

Changes

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.

2mo ago First seen · 117 lines · 932 tokens per session scan A 560126d6aec9

Subscribe to this mod's changes

lore-oss AGENTS.md is an instructions file published in the GitHub repository re-cinq/lore-oss (12 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 932 tokens to every session, about $0.0037 per session on Opus 5.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.

lore-oss AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lore-oss AGENTS.mdre-cinq/lore-oss	Instructions file	12	7mo ago	Apache-2.0	A	932	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

lore-oss: Instructions file for Codex