civic-ai-tools: Instructions file for Codex

AGENTS.md

civic-ai-tools AGENTS.md is an instructions file for Codex, OpenCode from npstorey/civic-ai-tools. It costs 1,549 tokens per session, scanned C, original, MIT.

Repository-specific instructions for civic-ai-tools, a project that connects agents to public-data sources such as NYC Open Data and Google Data Commons. It also documents shared standards, commands, configuration, and information boundaries.

In plain words
What is it for?
Guiding code changes, repository navigation, setup, MCP configuration, and publishing work in civic-ai-tools.
Why use it?
It gives coding agents the rules and context needed to work safely across the project’s four related repositories. It helps prevent private relationship details or secrets from being committed to the public codebase.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: reads ~/.codex or $CODEX_HOME, but also the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

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

Reuse

Borrowing it

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

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 civic-ai-tools AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/npstorey/civic-ai-tools/agents-md.svg)](https://agentmods.dev/instructions/npstorey/civic-ai-tools/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/npstorey/civic-ai-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/npstorey/civic-ai-tools/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,549 This file is loaded in full into every session.
When invoked 1,549 The same file — it is already loaded in full.
Security scan C 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.01549 $0.01549
Opus 5 $0.00775 $0.00775
Sonnet 5 $0.00310 $0.00310
Haiku 4.5 $0.00155 $0.00155

Measured 8d ago against content hash 294602877f27, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade C, and why

civic-ai-tools AGENTS.md scanned grade C 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 8d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- **Prove any install-path claim in a fresh `git clone`,** never an in-place `rm -rf node_modules`; npm 10.x runs
AGENTS.md · 81 lines

How it starts

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

AGENTS.md

The hub repo of a four-repo project: MCP configs and setup tooling for civic open data (NYC Open Data via Socrata, Google Data Commons), the Typed Standards Specification and its ADRs, the source of truth for shared skill guidance, and the publish-record skill. npm workspaces (one package, packages/civic-typed-harness) alongside Python examples. Cursor and Codex read this file natively; CLAUDE.md is a one-line bridge to it.

Boundaries

This repo is public. Strategic and relationship context — named external stakeholders, prospective collaborators, pre-meeting strategy, private outreach plans, named individuals' opinions — lives in local-only planning docs, never here. Use neutral phrasing ("an external stakeholder", "an upcoming demo") wherever output lands in this repo; if a prompt you received carries strategic context, scrub it first.

Never push to main, and never bypass a git hook or the pre-push sensitivity guard. The guard scans the added lines of each outgoing commit, not the net diff, so a fix commit on top never clears it — rebuild the branch history.

Secret hygiene (incident: civic#174, the 2026-08-22 token exposure). Never cat, head, tail, or otherwise dump .env*, auth.json, credentials*, *.pem, *.key, or anything under ~/.ssh or ~/.aws. Two reads are permitted: a field-scoped read by key name (grep '^VAR_NAME=' .env, or jq over non-secret fields), and a command the tool itself exposes (publish.py --list-tokens prints prefix, scope, and expiry only). One prohibition: never load-and-print a credentials file, even through a redaction filter — a filter applied at the wrong nesting level prints the value it was written to hide. Publish tokens live in ~/.config/civic-ai-tools/credentials.json; --logout is local-only, revocation is the dashboard. Setup keys belong in .env; tell a user to paste them there, never into a chat.

Commands

Command Healthy output
npm ci added 116 packages, and audited 118 packagesfound 0 vulnerabilities; leaves packages/civic-typed-harness/dist populated
npm run build the tsc -p tsconfig.json echo and nothing after it, exit 0
npm test # pass 125 / # fail 0 (node --test TAP; includes the golden byte-compat suite)
npm run typecheck no output, exit 0
npm run lint no output, exit 0
npm run check:budgets Dependency-budget check passed. — twin check:budgets:self-test# pass 9 / # fail 0
npm run check:spec-frontmatter Spec-frontmatter check passed. — twin check:spec-frontmatter:self-test# pass 11 / # fail 0
npm run check:skill-drift Skill-drift check passed — every embedded copy matches its source of truth. — twin check:skill-drift:self-test# pass 29 / # fail 0
python3 .claude/skills/publish-record/test_publish.py Ran 73 testsOK

Read the full file on GitHub · 81 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. 8d ago First seen · 81 lines · 1,549 tokens per session scan C 294602877f27

Subscribe to this mod's changes

civic-ai-tools AGENTS.md is an instructions file published in the GitHub repository npstorey/civic-ai-tools (41 stars, last pushed 3d ago), licensed MIT. It adds 1,549 tokens to every session, about $0.0077 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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

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

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

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,469 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens