Borrowing it
Nothing to install: this file belongs to civdotiq/civ.iq. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/civdotiq/civ.iq/main/CLAUDE.mdgit clone --depth 1 https://github.com/civdotiq/civ.iqWrote 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.
[](https://agentmods.dev/instructions/civdotiq/civ.iq/claude-md)<a href="https://agentmods.dev/instructions/civdotiq/civ.iq/claude-md"><img src="https://agentmods.dev/badge/instructions/civdotiq/civ.iq/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.00803 | $0.00803 |
| Opus 5 | $0.00402 | $0.00402 |
| Sonnet 5 | $0.00161 | $0.00161 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade C, and why
civ.iq CLAUDE.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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| Build fails | `rm -rf .next && npm run build` | How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.MD - CIV.IQ AI Assistant Instructions
Quick Context
Project: civic-intel-hub | Stack: Next.js 16 + TypeScript + React 18 Purpose: Civic intelligence platform using ONLY real government APIs (no mock data ever) Status: 100% TypeScript compliant, 249 API endpoints, 21 intelligence analyzers
Critical Rules (NEVER VIOLATE)
- Real Data Only: Use real government APIs or show "Data unavailable" - NEVER fake data
- TypeScript Strict: No
anytypes, full null safety with optional chaining - Quality Gates: All code must pass
npm run validate:allbefore completion - 30-Line Rule: Never write more than 30 lines without validation
- Clean Commits: Use conventional commits (feat/fix/docs/chore)
- Ask First: Clarify approach before implementing non-trivial features
Project Structure
src/
├── app/api/ # 249 API routes (real data only)
├── app/(civic)/ # Public pages
├── components/ # React components
│ └── intelligence/ # 35 insight cards and analysis displays
├── features/ # Feature modules (campaign-finance, legislation, representatives)
├── lib/ # Utilities and services
│ ├── intelligence/ # 21 analyzers, ML models, embeddings, entity resolution
│ ├── nostr/ # Nostr event signing and relay publishing
│ └── data-sources/ # Federal Register, FRED, SEC, lobbying services
├── types/ # TypeScript definitions
└── hooks/ # Custom React hooks
packages/ # npm workspaces — all three must be present for `npm ci`
├── civic-statistics/ # @civiq/civic-statistics
├── entity-resolution/ # @civiq/entity-resolution
└── sdk/ # @civiq/sdk — TypeScript client for the public API
Domain Rules (in .claude/rules/)
Detailed rules are decomposed into focused files loaded automatically:
- design-system.md — Aicher/Ulm School: colors, typography, borders, wayfinding, banned patterns
- intelligence-layer.md — Analyzer architecture, confidence scores, causation language, sample sizes
- security.md — Data integrity, API key handling, address-not-ZIP, input sanitization
- workflow.md — Guiding principles, workflow habits, when-stuck protocol
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 · 77 lines · 803 tokens per session scan C a796827bc404
civ.iq CLAUDE.md is an instructions file published in the GitHub repository civdotiq/civ.iq (0 stars, last pushed 4d ago), licensed Apache-2.0. It adds 803 tokens to every session, about $0.0040 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-31.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.