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/zackbart/connecta/agents-mdgit clone --depth 1 https://github.com/zackbart/connectaWhat 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.01891 | $0.01891 |
| Opus 5 | $0.00945 | $0.00945 |
| Sonnet 5 | $0.00378 | $0.00378 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
connecta 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 yesterday.
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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on connecta
This is the canonical instruction file for coding agents. CLAUDE.md is a
symlink to this file so every agent works from the same conventions.
A single MCP endpoint aggregating downstream connectors (remote MCP servers and
plain HTTP APIs) behind seven meta-tools, execute_code among them. Every
deployment configures an executor, and agents reach connectors by writing
JavaScript against it. One fetch-native core, running on both Node and
Cloudflare Workers.
ethos.mdis the constitution. It states what connecta is and isn't, and its decisions table carries a verdict for every shape already considered — refused, removed, provisional, or gated. Check the table before designing or building anything: arefusedrow is a "no" with the reason attached, and aremovedrow (toolkits #178, proactive credential liveness #179, the classic executor-free surface #273) records a surface that no longer exists — do not reintroduce it without a new decision.- There is no TODO.md — the roadmap lives in GitHub issues. When you find TODO items (in code comments, docs, or conversation), don't accumulate them in a file: turn each one into a GitHub issue that clearly defines what to do — motivation, behavioral requirements, and acceptance criteria — without prescribing the implementation.
Verification
npm run check must pass before you claim anything is done — check:docs →
check:operator-ui → check:lint → check:unused → typecheck → test
(both vitest projects) → build → check:examples. It is also the prepack
hook. npm run release:check adds check:security and check:package and is
what CI runs on publish; use it when touching packaging, dependencies, or
exports.
The map
ethos.md— what connecta is, what it refuses to be, the decisions table, and the invariants every change must preserve. Check it before building something new; "we already decided not to" is a real answer there, and its removed/provisional verdicts override anything staler.documentation/— per-subsystem guides for agents working on the repo. All of them are written now (#348); the retired manual (docs/<name>.md) survives only in git history, which is worth mining for rationale a rewrite dropped and worth nothing where it disagrees withethos.md. Start witharchitecture.md, then the guide for the subsystem you are changing.README.md— the human-facing overview.templates/node/— the one standalone Node deployment shape copied byconnecta init, Docker-ready rather than Docker-only. Keep it small and prescribed. There are exactly two deployment shapes, this one andexamples/worker/; a third scaffold that is a diff away from one of them is the shape #344 deleted.
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.
- yesterday First seen · 136 lines · 1,891 tokens per session scan A 1f13158ce525
connecta AGENTS.md is an instructions file published in the GitHub repository zackbart/connecta (0 stars, last pushed 2d ago), licensed MIT. It adds 1,891 tokens to every session, about $0.0095 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-31.
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.
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).
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.
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).
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.
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.