Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/axsaucedo/agent_data_duckdb/copilot-instructionsgit clone --depth 1 https://github.com/axsaucedo/agent_data_duckdbWrote 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/axsaucedo/agent_data_duckdb/copilot-instructions)<a href="https://agentmods.dev/instructions/axsaucedo/agent_data_duckdb/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/axsaucedo/agent_data_duckdb/copilot-instructions.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 | $0.01382 | $0.01382 |
| Opus 5 | $0.00691 | $0.00691 |
| Sonnet 5 | $0.00276 | $0.00276 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
agent_data_duckdb copilot-instructions.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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent_data DuckDB Extension - Development Instructions
Critical Caveats
1. JSONL File Handling - DANGER ZONE
⚠️ NEVER print, cat, or view full JSONL files from claude_raw/, copilot_raw/ or test/data/
The JSONL conversation files can be massive (hundreds of MB). Incorrect commands will:
- Pollute the entire context window
- Cause memory issues
- Result in incomplete/corrupted output
Safe Commands:
# View first N bytes only
head -c 500 file.jsonl
# Count lines without reading content
wc -l file.jsonl
# Get first N complete JSON lines
head -n 3 file.jsonl | jq -c '.'
# Sample specific fields only
head -n 10 file.jsonl | jq -c '{type, timestamp}'
# Get file size
ls -lh file.jsonl
NEVER DO:
cat file.jsonl # DANGEROUS
less file.jsonl # DANGEROUS (without limits)
jq '.' file.jsonl # DANGEROUS (reads entire file)
2. Build and Test
make configure # First time setup
make debug # Build debug extension
make test # Build + run all tests
3. Testing Strategy
- Always run tests with limited data first
- Use
test/data/(Claude) andtest/data_copilot/(Copilot) synthetic data - Never use
claude_raw/orcopilot_raw/for automated tests - Run
make testafter every change - Tests are assertion-driven (PASS/FAIL output)
Project Structure
agentic-copilot/
├── .copilot-instructions.md # THIS FILE
├── Cargo.toml # Rust crate (agent_data)
├── Makefile # Build system
├── src/ # Rust extension source
│ ├── lib.rs # Entry point (registers 5 functions)
│ ├── vtab.rs # Generic VTab framework (TableFunc trait)
│ ├── detect.rs # Provider auto-detection (Claude/Copilot)
│ ├── types/
│ │ ├── mod.rs # Re-exports
│ │ ├── claude.rs # Claude JSON/JSONL serde types
│ │ └── copilot.rs # Copilot event serde types
│ ├── utils.rs # Path resolution, file discovery (both providers)
│ ├── conversations.rs # Unified read_conversations()
│ ├── plans.rs # Unified read_plans()
│ ├── todos.rs # Unified read_todos()
│ ├── history.rs # Unified read_history()
│ └── stats.rs # read_stats() (Claude only)
├── test/
│ ├── data/ # Synthetic Claude data (~/.claude mock)
│ ├── data_copilot/ # Synthetic Copilot data (~/.copilot mock)
│ └── sql/ # SQL test files (104+ assertions)
├── scripts/
│ ├── test.sh # SQL test runner
│ └── smoke_test.sh # Python/DuckDB smoke test
├── examples/
│ └── explore.py # Marimo notebook (multi-source)
├── docs/ # Documentation
│ ├── CLAUDE_FILE_STRUCTURE.md
│ ├── CLAUDE_FILE_SCHEMAS.md
│ ├── COPILOT_FILE_STRUCTURE.md
│ ├── COPILOT_FILE_SCHEMAS.md
│ └── DUCKDB_EXTENSION_PATTERNS.md
├── claude_raw/ # Real Claude data - READ ONLY, HANDLE WITH CARE
└── copilot_raw/ # Real Copilot data - READ ONLY, HANDLE WITH CARE
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.
- 4d ago First seen · 150 lines · 1,382 tokens per session scan A c560f1c91b0b
agent_data_duckdb copilot-instructions.md is an instructions file published in the GitHub repository axsaucedo/agent_data_duckdb (24 stars, last pushed 1mo ago), licensed MIT. It adds 1,382 tokens to every session, about $0.0069 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-08-30.
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.