agentleFS
Sign inStart free
Rick1330Rick1330/ibex-harness/.github/copilot-instructions.md

ibex-harness

Copilot instructions57 starsChanged 13 days agoMITView on GitHub

Read AGENTS.md and engineering/agent-playbook.md before suggesting changes. AGENTS.md is authoritative; this file is a short entry point. IBEX is a self-hosted memory and context layer for multi-tenant AI agents. The Console is the operations plane for the agent → session → memory → evidence lifecycle and is built with Nuxt 4 + Vue 3 + Nitro (ADR-0088, ADR-0089). Suggest the narrowest relevant commands from engineering/agent-playbook.md §6, for example: Use engineering/DEVELOPMENT_GUIDE.md §4.4 for real service startup commands. Do not invent make…

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,336 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository7 other files it gives its agents.

The file

We split this copilot-instructions.md into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read AGENTS.md and engineering/agent-playbook.md before suggesting changes.

    line 3
  2. Very specific:

    Keep explicit org_id filtering in every data path, even with PostgreSQL RLS.

    line 13
  3. Distinctive:

    Never emit secrets, tokens, memory content, prompts, or personal data in logs, tests, or examples.

    line 14
  4. Distinctive:

    No placeholder logic, stubbed success handlers, or speculative dependencies.

    line 15
  5. Distinctive:

    Do not weaken lint, tests, coverage, or CI gates.

    line 16
  6. Very specific:

    Every commit needs Signed-off-by (git commit -s).

    line 17
  7. Very specific:

    Use engineering/DEVELOPMENT_GUIDE.md §4.4 for real service startup commands.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

GitHub Copilot instructions — IBEX Harness

Read AGENTS.md and engineering/agent-playbook.md before suggesting changes. AGENTS.md is authoritative; this file is a short entry point.

Product shape

IBEX is a self-hosted memory and context layer for multi-tenant AI agents. The Console is the operations plane for the agent → session → memory → evidence lifecycle and is built with Nuxt 4 + Vue 3 + Nitro (ADR-0088, ADR-0089).

Non-negotiables

  • Keep explicit org_id filtering in every data path, even with PostgreSQL RLS. Cross-tenant reads return 404.
  • Never emit secrets, tokens, memory content, prompts, or personal data in logs, tests, or examples.
  • No placeholder logic, stubbed success handlers, or speculative dependencies.
  • Do not weaken lint, tests, coverage, or CI gates.
  • Every commit needs Signed-off-by (git commit -s).
  • Surface status is defined in services/console/shared/operator/surfaces.ts; do not restate it.

Validation

Suggest the narrowest relevant commands from engineering/agent-playbook.md §6, for example:

make check
pnpm --filter @ibex/console test && pnpm --filter @ibex/console typecheck && pnpm --filter @ibex/console lint
pnpm site:build && pnpm site:check

Use engineering/DEVELOPMENT_GUIDE.md §4.4 for real service startup commands. Do not invent make dev-* targets.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free