apifable: Instructions file for Codex

AGENTS.md

apifable AGENTS.md is an instructions file for Codex, OpenCode from ycs77/apifable. It costs 771 tokens per session, scanned A, original, MIT.

A set of repository instructions for apifable, including required versions, formatting rules, build and test commands, configuration precedence, and project-specific constraints.

In plain words
What is it for?
Use it when working on apifable to choose the right Node.js, Zod, MCP, bundler, formatting, linting, type-checking, and test conventions.
Why use it?
It gives coding agents the rules they must follow in that repository and records behaviors that are easy to miss during changes.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ycs77/apifable/agents-md"><img src="https://agentmods.dev/badge/instructions/ycs77/apifable/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 771 This file is loaded in full into every session.
When invoked 771 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.00771 $0.00771
Opus 5.5 $0.00308 $0.00308
Sonnet 5.5 $0.00154 $0.00154
Haiku 4.5 $0.00077 $0.00077

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

Security

Grade A, and why

apifable 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 · 49 lines

How it starts

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

AGENTS.md

Keep This File Strict

  • Do not add repo tours, architecture summaries, or file inventories.
  • Only keep constraints, non-obvious behavior, and things an agent must not do.
  • If a fact is easy to find with grep, it probably does not belong here.

Constraints

  • Node.js v22+
  • Zod v4
  • MCP SDK protocol version 2025-11-25 (stable)
  • Bundler is tsdown, not tsc
  • TypeScript formatting: 2 spaces, single quotes, no semicolons, trailing commas

Commands

  • pnpm build
  • pnpm lint --fix
  • pnpm lint [...files] --fix
  • pnpm fmt
  • pnpm fmt [...files]
  • pnpm typecheck
  • pnpm test --run

Rules

  • Config priority: CLI flag > config > default value
  • Prefer pure-function tests first; controlled temp-dir fs tests are allowed, but skip MCP handlers, CLI code, prompt flows, process.exit paths, and real network calls
  • Do not reintroduce ParsedSpec cache assumptions; parsed specs are built directly

Non-Obvious Behavior

  • HTTP_METHODS and isValidHttpMethod live in src/http-methods.ts; do not re-declare method lists in tools or parsers
  • search_endpoints default limit is 10; max is 100
  • search_schemas default limit is 10; max is 100
  • search_endpoints and search_schemas return real match count in total; truncated responses use hasMore
  • search_endpoints fuzzy fallback uses MiniSearch with fuzzy: 0.2 and prefix matching; response includes matchType, fuzzy results include score, empty fuzzy results include message
  • get_endpoint validates mutually exclusive modes in the tool function, not the handler; valid modes are method + path or operationId; empty operationId is an error
  • get_endpoint, get_types, get_schema, and list_endpoints_by_tag use src/tools/suggestions.ts for guided not-found errors; findSimilarNames tries substring matches before MiniSearch fuzzy fallback and returns up to 5 suggestions
  • list_endpoints_by_tag supports limit and offset; response includes total, offset, hasMore; warn when total > 30 && limit === undefined
  • get_types accepts exactly one mode per call: schemas, method + path, or operationId; mixing modes is an error
  • get_types returns self-contained TypeScript declarations as code text with no imports
  • get_types supports inline JSON request/response schemas through src/tools/inline-schemas.ts; names are {PascalOperationId}Request|Response or {Method}{NormalizedPath}Request|Response when there is no operationId
  • Inline schema extraction only promotes top-level non-$ref JSON request schemas and first 2xx response schemas to inline roots; nested $ref values still use normal dependency tracking
  • Zod schemas use .loose() to allow unknown keys; path-specific errors for invalid known field types (not .passthrough() which is deprecated in Zod v4)
  • Auth headers live in .apifable/auth.json and are not version-controlled; spec.headers in config is for non-secret headers; auth values override config on key conflict; both support ${ENV_VAR} expansion and keep undefined vars unchanged

Read the full file on GitHub · 49 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 First seen · 49 lines · 771 tokens per session scan A 36da8bd3c774

Subscribe to this mod's changes

apifable AGENTS.md is an instructions file published in the GitHub repository ycs77/apifable (10 stars, last pushed 8d ago), licensed MIT. It adds 771 tokens to every session, about $0.0031 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,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