modsearch: Instructions file for Codex

AGENTS.md

modsearch AGENTS.md is an instructions file for Codex, OpenCode from liustack/modsearch. It costs 1,965 tokens per session, scanned A, original, MIT.

Project instructions for modsearch, a command-line tool that turns web searches and page fetches into structured evidence for AI agents. It describes the tool's engines, configuration, code layout, and skills.

In plain words
What is it for?
Use it when developing modsearch, adding or changing search engines, configuring automatic search, or working on its command-line behaviour.
Why use it?
It helps an agent understand how modsearch searches, fetches pages, selects search engines, and returns validated JSON results.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Gemini CLI.

This is liustack/modsearch's own configuration. It tells Codex and OpenCode how to work on modsearch 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 modsearch configures →

Reuse

Borrowing it

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

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 modsearch AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/liustack/modsearch/agents-md"><img src="https://agentmods.dev/badge/instructions/liustack/modsearch/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,965 This file is loaded in full into every session.
When invoked 1,965 The same file — it is already loaded in full.
Security scan A 1 finding. 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.01965 $0.01965
Opus 5.5 $0.00786 $0.00786
Sonnet 5.5 $0.00393 $0.00393
Haiku 4.5 $0.00197 $0.00197

Measured 11d ago against content hash da64786a04dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

modsearch AGENTS.md scanned grade A with 1 finding 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 11d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- **Hidden Windows children**: the core and standalone dsh plugin each own one child-process wrapper that forces `windowsHide: true`. A contract test rejects direct `child_process` access anywhere else in shipped code.
AGENTS.md · 118 lines

How it starts

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

Project Overview (for AI Agent)

Goal

Provide the modsearch CLI tool that turns search queries and page URLs into structured web evidence for LLM agent workflows.

Technical Approach

  • Pluggable engines — the engine interface (buildInvocation + parseOutput for subprocess engines, or execute for in-process ones) keeps each engine contained to one file, so adding or swapping one touches nothing else. Antigravity CLI (agy) is the preferred search engine when it is available.
  • Two modes, one CLI: -q searches the web, -u fetches a single page (absorbed from the retired modfetch project). -u plus -q fetches with an answer focus.
  • Schema-enforced JSON output: subprocess engines are invoked with --json-schema, so the structured result comes back guaranteed, no markdown scraping. grok-cli is the exception: that flag disables its search loop, so the result is salvaged from the final text.
  • Selectable automatic chain: every engine participates by default. engines.<name>.enabled: false excludes one from automatic search, fetch, or X routing. An explicit --engine still forces a one-off run. doctor reports readiness and enabled state separately.
  • Hidden Windows children: the core and standalone dsh plugin each own one child-process wrapper that forces windowsHide: true. A contract test rejects direct child_process access anywhere else in shipped code.
  • Single responsibility: this project handles the live web (search + fetch). Image parsing lives in modlens.
  • X handling: X-flavored -q queries route entirely to Grok Build (grok-cli) when it is installed and signed in, spending no agy quota. When Grok is missing or fails, a web engine answers instead, and that entry is marked status: "degraded" with source: "web" and requestedSource: "x" so the second-hand nature is explicit, never silent. On a --source web,x run with X unreachable, the X slot returns a separate status: "unavailable" entry rather than vanishing. An explicit -e/--engine is a hard force: exactly that engine, no fallback, an error if it cannot do the job. One shared output contract for every engine.

Read the full file on GitHub · 118 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. 11d ago Changed · +1 lines · +20 tokens per session da64786a04dd
  2. 1mo ago Changed · +44 tokens per session 03fcfb8646e5
  3. 1mo ago Changed · -2 tokens per session 2324b5256321
  4. 1mo ago Changed · +25 tokens per session d7eca8ce0c77
  5. 1mo ago First seen · 117 lines · 1,878 tokens per session scan A 709f0a4af067

Subscribe to this mod's changes

modsearch AGENTS.md is an instructions file published in the GitHub repository liustack/modsearch (846 stars, last pushed 9d ago), licensed MIT. It adds 1,965 tokens to every session, about $0.0079 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

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,786 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,731 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