agentmods.dev

ask-llm: Instructions file for Codex

AGENTS.md

ask-llm AGENTS.md is an instructions file for Codex, OpenCode from Lykhoyda/ask-llm. It costs 1,830 tokens per session, scanned A, original, MIT.

Project instructions for ask-llm, a codebase that connects applications to language-model providers. They record build, test, documentation, architecture, and provider-specific rules for AI agents working on the project.

In plain words
What is it for?
It is for maintaining the ask-llm project: installing dependencies, building packages, running tests and linting, updating architecture decisions, and keeping provider documentation aligned with code.
Why use it?
They keep important project knowledge in the repository so agents can follow the required build order and avoid breaking documented provider differences. They also identify checks for documentation and code consistency.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code; runs codex exec; mentions Codex.

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

not rated 18repo changed 15d ago A scan 1,830 tokens original MIT
View source ↗ Lykhoyda/ask-llm lykhoyda.github.io
Reuse

Borrowing it

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

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 ask-llm AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/lykhoyda/ask-llm/agents-md"><img src="https://agentmods.dev/badge/instructions/lykhoyda/ask-llm/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,830 This file is loaded in full into every session.
When invoked 1,830 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.01830 $0.01830
Opus 5.5 $0.00732 $0.00732
Sonnet 5.5 $0.00366 $0.00366
Haiku 4.5 $0.00183 $0.00183

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

Security

Grade A, and why

ask-llm 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 15d 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 · 25 lines

How it starts

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

Project agent memory

This file is the project's committed home for project-intrinsic agent knowledge: build, test, release, architecture, and sharp-edge notes that should travel with the code.

  • Build/test: yarn install --immutable, then yarn build (topological — run it BEFORE yarn test; workspace tests resolve sibling packages from dist/, so unbuilt @ask-llm/shared fails every suite). Lint via yarn lint (biome format is enforced; biome check --write fixes). Harness-facing changes use the canonical local-only yarn prepr:harness gate; opt-in live authorization and evidence rules are in docs/HARNESS-SMOKE.md. Supported platforms are Linux and macOS (CI: Ubuntu Node 24 five-batch plus pi-lifecycle-macos); every package requires Node 24, the current LTS (ADR-171); do not add Windows jobs or claim Windows support (ADR-159). Claude GitHub Action is @claude on demand only (ADR-160); do not restore automatic PR review via claude-code-review.yml.
  • Every packages/llm-mcp/scripts/**/*.mjs is generated from a TypeScript 7 .mts sibling and committed (marketplace git-subdir installs cannot build): after editing an .mts, run yarn workspace @ask-llm/mcp build:hooks and commit both; never add or hand-edit a .mjs there (generated-hooks.test.ts enforces this, ADR-170/171).
  • Repo-root scripts/*.ts (and test fixtures) are plain TypeScript run directly by Node 24 type stripping, with no build step: import siblings as ./x.ts, use erasable syntax only; yarn lint typechecks them. No other .js/.mjs/.cjs may be committed (ADR-172, scripts/typescript-contract.test.ts).
  • Architecture decisions live in docs/DECISIONS.md (numbered ADRs, newest prepended at the top); provider behavior differences are deliberate and cataloged in docs/PROVIDER-PARITY.md — read both before "aligning" providers.
  • Docs-model drift is CI-enforced: scripts/check-docs-drift.ts requires apps/docs/.vitepress/theme/providers.ts defaultModel (and gemini/antigravity fallbackModel) values to match each package's constants.ts literally, matched inside each provider's own object block. Change both together.
  • MCP Registry rejects duplicate versions. Keep normal and recovery publication routed through scripts/publish-mcp-registry.ts; it verifies exact existing records and publishes only missing ones (ADR-139), after waiting up to 10 min for npm to show each selected version (ADR-174). Manual Release dispatch has no inputs: on main it always repairs Registry, the unified GitHub Release, and per-package tags, and must not re-enter npm publication (ADR-158).
  • Public package source tags are remote <name>@<version> refs managed only by scripts/create-or-verify-package-tags.ts on normal and recovery release paths (ADR-151/152); changesets/action v2 must keep both create-github-releases: false and push-git-tags: false, while the helper excludes private shared, never retags/forces, and also creates or verifies @ask-llm/mcp@<version> for the single unified GitHub Release (ADR-181). Changesets 3 publishes via yarn npm publish, so release.yml must pass YARN_NPM_AUTH_TOKEN from secrets.NODE_AUTH_TOKEN (ADR-156); NODE_AUTH_TOKEN alone authenticates npm CLI steps only. After publish, npm access set status=public is verify-first and must not fail the job on 401/403 when packages are already public or the token cannot change access (ADR-157).
  • Gemini quota fallback is gemini-3.8-flash (ADR-155); the antigravity fallback is also gemini-3.8-flash but on independent evidence (ADR-178: agy's base slug + --effort; agy models lists only tiered ids like gemini-3.8-flash-high, which conflict with --effort) — agy slugs are evidence-pinned to its live catalog (ADR-137), so never bump both in sympathy.
  • Provider default-model constants leak further than the provider package: packages/llm-mcp/src/constants.ts (PROVIDERS.*.defaultModel) is threaded into executors as options.model by machine.ts, so executors cannot use "was a model passed?" to detect user pins (see ADR-137).
  • Antigravity MCP and machine execution refuse before agy spawn unless ASK_ANTIGRAVITY_ALLOW_UNISOLATED=1; the raw /brainstorm participant skips by default. Opt-in has no read-only guarantee (ADR-177).
  • agy (Antigravity) CLI ground truth for this repo's executor is recorded in ADR-137 (minimum 1.1.5, base slug + separate --effort, per-slug effort tiers, the live-captured invalid model selection error grammar), ADR-141 (answers come from --output-format json stdout — key response, usage object — on every supported version; --disable-slash-commands is 1.1.9+ only), ADR-162 (agy ≥1.1.28 --print-timeout expiry is exit 0 with a truncated answer; fail closed, do not serve it as complete), and ADR-178 (agy ≥1.2.6 exit-3 AGY_ERROR: stderr line: classify only its compacted fields, never the opaque error_id).
  • Grok transport and model identity are separate (ADR-146/147; /brainstorm exact Grok + Sol routing and partial-consensus rules are in ADR-148): unified startup probes both xai-api and grok-cli readiness because request-level harness selection happens later (an explicit ASK_GROK_HARNESS narrows readiness to that default), but execution selects exactly one explicit/default harness with no failover; Cursor Agent is a model-neutral harness (ask-cursor-agent) requiring separate provider + exact Cursor catalog ID, never a provider itself.
  • @ask-llm/mcp owns the Claude Code + Cursor Agent + Pi host assets, with @ask-llm/plugin as a dependent compatibility bridge (ADR-142/147/161); host contracts live in the skill adapters, apps/docs/compatibility/cursor.md, and docs/PI-COMPATIBILITY.md. Cursor uses Agent Skills + a unified-only mcp.json (one ask-llm entry; split Codex/Grok servers are optional user installs whose leaves are preferred when exposed) exposing exactly ask-llm-codex-pair/ask-llm-grok-pair plus their old-name pointers (explicit empty agents/commands/hooks so Claude agents and hooks/hooks.json are not auto-discovered; ask-llm setup installs the rest of the portable corpus through the skills CLI), never Claude hooks/namespaces; the Claude plugin .mcp.json bundles only Codex while @ask-llm/mcp/@ask-llm/grok-mcp stay user-scoped. Codex-facing plugin workflows prefer any ask-codex leaf, then fully pinned unified ask-llm (provider, model, reasoningEffort, includeDirs, preferred, sandbox; older schemas fail closed), then disclosed codex exec; pair skills call unified ask-llm only fully pinned. Pi's package manifest ships only the extension (native provider tools) and Pi reads the skills from the folder ask-llm setup fills (ADR-183), and codex-pair requires marker + project trust + a user-owned canonical-project allowlist. The published Pi host floor must equal the oldest exact pi-package-smoke matrix pin (currently 0.83.0).

Read the full file on GitHub · 25 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. 15d ago Changed · +2 tokens per session 30331f62ce24
  2. 26d ago Changed · +44 tokens per session fad514f0a5a5
  3. 29d ago Changed · +14 tokens per session 0d8b6a805059
  4. 1mo ago Changed · +15 tokens per session ade8ab3a86c6
  5. 1mo ago Changed · +2 lines · +249 tokens per session 959a99fdf27b
  6. 1mo ago Changed · +1 lines · +94 tokens per session f25af4907b7a
  7. 1mo ago Changed · +37 tokens per session df03ebe6cf85
  8. 1mo ago Changed · +91 tokens per session ff4279d28b68
  9. 1mo ago Changed · +42 tokens per session 3fdf4d3c5df6
  10. 1mo ago First seen · 22 lines · 1,242 tokens per session scan A 3d3351ff44c8

Subscribe to this mod's changes

ask-llm AGENTS.md is an instructions file published in the GitHub repository Lykhoyda/ask-llm (18 stars, last pushed today), licensed MIT. It adds 1,830 tokens to every session, about $0.0073 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.

Building agentsClaude Codeaiclaudeclaude-aiclaude-mcpgemini
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,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens