delve: Instructions file for Codex

AGENTS.md

delve AGENTS.md is an instructions file for Codex, OpenCode from robcsaszar/delve. It costs 576 tokens per session, scanned A, original, MIT.

A set of AGENTS.md instructions for the delve project. AGENTS.md is a file that tells a coding agent how to work in a repository.

In plain words
What is it for?
Guiding agent work on the delve repository and checking that its skill content does not contain source-project-specific references.
Why use it?
It gives the agent project-specific guidance about the mission, acceptable changes, and checks to run before publishing.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions .claude-plugin; mentions AGENTS.md.

This is robcsaszar/delve's own configuration. It tells Codex and OpenCode how to work on delve itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything delve configures →

Reuse

Borrowing it

Nothing to install: this file belongs to robcsaszar/delve. 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/robcsaszar/delve/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/robcsaszar/delve

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.

agentmods badge for delve AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/robcsaszar/delve/agents-md/github.svg)](https://agentmods.dev/instructions/robcsaszar/delve/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/robcsaszar/delve/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/delve/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.

agentmods 80×15 button for delve AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/robcsaszar/delve/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/delve/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 576 This file is loaded in full into every session.
When invoked 576 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00576 $0.00576
Opus 5.5 $0.00230 $0.00230
Sonnet 5.5 $0.00115 $0.00115
Haiku 4.5 $0.00058 $0.00058

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

Security

Grade A, and why

delve 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 1mo 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 · 39 lines

How it starts

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

AGENTS.md

Mission

This repo publishes a single skill, delve, copied in from a source repo (Orakl) where it is used and refined, then published here for anyone to install. There is no build, no tests, no runtime of its own. The deliverable is skills/delve/.

Judgment boundary

Don't let the skill's content drift toward being useful only in one narrow context. It exists to make any agent a more careful, confidence-flagging research collaborator on any topic; a change that only makes sense for one specific domain or project doesn't belong here. If you're updating it, re-run a grep for source-repo-specific leakage (grep -rni "orakl" under skills/) before publishing.

Releasing

Releases are cut by the Release workflow (.github/workflows/release.yml), never by hand. It is a manual workflow_dispatch with one input, tag, and it releases the commit at the tip of the branch it is run on. Run it on main.

The workflow, in order:

  1. Rejects a tag that is not vX.Y.Z, or that already exists.
  2. Fails unless version in .claude-plugin/plugin.json and plugins[0].version in .claude-plugin/marketplace.json both equal X.Y.Z.
  3. Takes the ## [X.Y.Z] block from CHANGELOG.md as the release notes, and fails if there is none.
  4. Creates the tag at the checked-out commit and publishes the GitHub release with those notes.

Nothing is created until every check passes, so a failed run leaves nothing to clean up.

To prepare a release, in one PR:

  • Set the same new version in .claude-plugin/plugin.json and .claude-plugin/marketplace.json.
  • Add a ## [X.Y.Z] - YYYY-MM-DD block at the top of CHANGELOG.md, and its [X.Y.Z]: … link reference at the bottom.
  • Merge to main.

Then run the workflow on main with tag=vX.Y.Z, from the Actions tab (Release → Run workflow) or from a shell:

gh workflow run release.yml --ref main -f tag=vX.Y.Z

Afterwards, confirm the release exists and its notes match the changelog block.

NEVER:

  • Never push a tag or create a release outside the workflow. A hand-made tag makes the workflow refuse that version, and a hand-written release skips the changelog and version checks.
  • Never work around a failed run by hand-writing notes or skipping a check. Fix the changelog or the manifests, merge, and re-run.

Read the full file on GitHub · 39 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.

  1. 1mo ago Changed · +29 lines · +418 tokens per session 3b71aa477bbb
  2. 2mo ago First seen · 10 lines · 158 tokens per session scan A 664e32343d20

Subscribe to this mod's changes

delve AGENTS.md is an instructions file published in the GitHub repository robcsaszar/delve (0 stars, last pushed 1mo ago), licensed MIT. It adds 576 tokens to every session, about $0.0023 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-31.

Related

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

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens