What is volterra-knowledge-engine AGENTS.md?

A set of repository instructions for the Volterra knowledge-engine project. It documents the project layout, development commands, coding conventions, testing guidance, database migrations, and data-ingestion tools.

Use it when working on the project's TypeScript source, Supabase database and functions, configuration, documentation, ingestion scripts, or n8n workflows.

It gives coding agents the project-specific rules needed to make compatible changes and run the right checks.

How duhman/volterra-knowledge-engine configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to duhman/volterra-knowledge-engine. 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/duhman/volterra-knowledge-engine/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/duhman/volterra-knowledge-engine

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/duhman/volterra-knowledge-engine/agents-md/github.svg)](https://agentmods.dev/instructions/duhman/volterra-knowledge-engine/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/duhman/volterra-knowledge-engine/agents-md"><img src="https://agentmods.dev/badge/instructions/duhman/volterra-knowledge-engine/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/duhman/volterra-knowledge-engine/agents-md"><img src="https://agentmods.dev/badge/instructions/duhman/volterra-knowledge-engine/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 659 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.00659	$0.00659
Opus 5.5	$0.00264	$0.00264
Sonnet 5.5	$0.00132	$0.00132
Haiku 4.5	$0.00066	$0.00066

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

Security

Grade A, and why

volterra-knowledge-engine 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 2mo 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 · 42 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

src/ holds the TypeScript source. Key areas: core/ (pipeline orchestration), parsers/ (file format extraction), sources/ (Notion/SharePoint/HubSpot/Slack/file), services/ (n8n client), compliance/ (PII/GDPR), database/ (Supabase client + migrations), scripts/ (CLI entry points), and types/.
supabase/migrations/ contains timestamped SQL migrations that must be applied in order.
supabase/functions/ contains Edge Functions for daily syncs (Notion, Slack, HubSpot).
config/default.json is the non-secret runtime configuration. docs/ houses operational documentation.
Claude skills live in .claude/skills/ (e.g. volterra-kb/, n8n/).

Build, Test, and Development Commands

npm run dev runs tsx watch for local development.
npm run build compiles TypeScript to dist/; npm run start runs dist/index.js.
npm run typecheck runs tsc --noEmit for static checks.
Ingestion entry points live in src/scripts/ (e.g., npm run ingest:file, npm run ingest:notion, npm run ingest:slack -- --export-path /path).
npm run n8n manages n8n workflows (list/get/update/etc.), incl test + patch-supabase.
npm run test:slack-env validates Slack Edge Function configuration.

Coding Style & Naming Conventions

TypeScript ESM ("type": "module"), strict mode; import paths include .js extensions.
Indentation is 2 spaces; prefer small, focused modules.
Naming: PascalCase for classes, camelCase for functions/vars, kebab-case for filenames (e.g., batch-ingest.ts).
No formatter/linter is configured; keep style consistent with nearby files.

Testing Guidelines

There is no dedicated test framework or tests/ directory.
Validate changes with npm run typecheck and by running the relevant CLI script(s) for the area you touched (ingestion, sync, or training tools).

Commit & Pull Request Guidelines

Recent commit messages are sentence-case, descriptive summaries (e.g., “Add Notion integration features…”). Follow that pattern.
PRs should include: a brief summary, any new/updated env vars, migration files (if schema changes), and the exact commands used to validate changes.
If adding migrations, note they must be run manually in Supabase SQL Editor and consider updating src/types/database.types.ts.

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

2mo ago First seen · 42 lines · 659 tokens per session scan A 66c0ffcbd9da

Subscribe to this mod's changes

volterra-knowledge-engine AGENTS.md is an instructions file published in the GitHub repository duhman/volterra-knowledge-engine (0 stars, last pushed 8mo ago), licensed MIT. It adds 659 tokens to every session, about $0.0026 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.

Document Ingestion ai embeddings gdpr knowledge-base mcp

volterra-knowledge-engine AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
volterra-knowledge-engine AGENTS.mdduhman/volterra-knowledge-engine	Instructions file	0	8mo ago	MIT	A	659	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

volterra-knowledge-engine: Instructions file for Codex