What is public-record-data-scrapper AGENTS.md?

Repository instructions for a public-record data scraper, a program that collects information from government or other publicly available records. They describe its source layout, web application, server, database, infrastructure, and development commands.

Use them as a reference when working on the scraper's frontend, API, workers, scripts, database, infrastructure, or tests.

They give coding agents and contributors the project-specific rules needed to change, build, and test the repository safely.

How organvm-iii-ergon/public-record-data-scrapper configures Codex and

Reuse

Borrowing it

Nothing to install: this file belongs to organvm-iii-ergon/public-record-data-scrapper. 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/organvm-iii-ergon/public-record-data-scrapper/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/organvm-iii-ergon/public-record-data-scrapper

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/organvm-iii-ergon/public-record-data-scrapper/agents-md/github.svg)](https://agentmods.dev/instructions/organvm-iii-ergon/public-record-data-scrapper/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/organvm-iii-ergon/public-record-data-scrapper/agents-md"><img src="https://agentmods.dev/badge/instructions/organvm-iii-ergon/public-record-data-scrapper/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/organvm-iii-ergon/public-record-data-scrapper/agents-md"><img src="https://agentmods.dev/badge/instructions/organvm-iii-ergon/public-record-data-scrapper/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 822 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.00822	$0.00822
Opus 5	$0.00411	$0.00411
Sonnet 5	$0.00164	$0.00164
Haiku 4.5	$0.00082	$0.00082

Measured 7d ago against content hash 32de494ff812, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

public-record-data-scrapper 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 7d 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 · 69 lines

How it starts

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

Repository Guidelines

Global policy: /Users/4jp/AGENTS.md applies and cannot be overridden.

Project Structure & Module Organization

src/ contains the Vite/React app. Key areas: components/ (UI and feature components), components/ui/ (Radix wrappers), hooks/, lib/ (agentic engine, collectors, scrapers, services), styles/, and types/.
server/ is the Express API and worker process for queues and background jobs.
scripts/ holds CLI utilities (scraping, DB tasks, video tooling).
tests/ contains integration/ and e2e/ suites. Unit tests live alongside code in src/**/__tests__ and *.test.ts(x).
database/ has schema files; terraform/ and k8s/ cover infrastructure; public/ stores static assets.

Build, Test, and Development Commands

npm install installs dependencies (Node 18+ recommended).
npm run dev starts the Vite dev server (port 5000).
npm run build runs the TypeScript build step (no diagnostics) and Vite production build; npm run preview serves the build.
npm run lint runs ESLint.
npm test runs Vitest; npm run test:coverage generates coverage.
npm run test:e2e runs Playwright; npm run test:scrapers:ca targets a single state.
npm run scrape -- scrape-ucc -c "Company" -s CA -o results.json runs the CLI scraper.
npm run db:migrate and npm run db:test handle database setup checks.

Coding Style & Naming Conventions

TypeScript + React. Follow React hooks rules and keep components focused and reusable.
Prettier config: 2-space indentation, single quotes, no semicolons, 100 column print width. ESLint enforces code quality.
Use PascalCase for components, useX for hooks, and *.test.ts(x) for tests.
Update src/lib/types.ts first when changing data shapes.

Testing Guidelines

Unit and integration tests: Vitest with jsdom (src/**/__tests__, *.test.ts).
Integration suites: tests/integration/.
End-to-end: Playwright in tests/e2e/.
Run the smallest relevant suite before PRs, then full npm test if you touched shared logic.

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

7d ago First seen · 69 lines · 822 tokens per session scan A 32de494ff812

Subscribe to this mod's changes

public-record-data-scrapper AGENTS.md is an instructions file published in the GitHub repository organvm-iii-ergon/public-record-data-scrapper (8 stars, last pushed today), licensed MIT. It adds 822 tokens to every session, about $0.0041 per session on Opus 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-09-04.

Backend and APIs Frontend alternative-lending data-enrichment lead-generation lead-scoring merchant-cash-advance public records

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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 · 6,785 tokens

public-record-data-scrapper: Instructions file for Codex