consent copilot-instructions.md

Repository instructions for developing Consent, a software project built with Dropwizard, Guice, and JDBI. They define its code structure, authentication rules, API compatibility requirements, formatting, performance, and testing expectations.

In plain words
What is it for?
Use them when implementing features, changing API routes, reviewing code, updating API documentation, or working with large database-backed results in the Consent repository.
Why use it?
They help coding agents make changes that fit the existing architecture and avoid breaking authentication, public APIs, database access, or quality checks.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/databiosphere/consent/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/DataBiosphere/consent

Made for: GitHub Copilot.

Per session 420 This file is loaded in full into every session.
When invoked 420 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00420 $0.00420
Opus 5 $0.00210 $0.00210
Sonnet 5 $0.00084 $0.00084
Haiku 4.5 $0.00042 $0.00042

Measured 2d ago against content hash 4a4a3a303044, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

consent 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 2d 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.

.github/copilot-instructions.md · 43 lines

What it actually says

These instructions apply to code suggestions and PR review in this repository.

Architecture and Boundaries

  • Keep the existing Dropwizard + Guice + JDBI architecture.
  • Preserve Resource -> Service -> DAO separation.
  • Prefer incremental changes to broad rewrites.
  • Reuse existing auth and error handling patterns (@RolesAllowed, Resource.createExceptionResponse, org.broadinstitute.consent.http.mappers ExceptionMappers).

API and Auth Rules

  • Auth boundary is route-based:
    • Paths under /api are authenticated through the proxy Auth section and include OAUTH-decorated request information.
    • Non-/api paths are unauthenticated and must not assume OAUTH context.
  • Put authenticated endpoints under /api.
  • Keep public API behavior backward compatible unless explicitly approved.
  • If API contracts change, update OpenAPI spec in src/main/resources/assets/api-docs.yaml.

Quality and Performance Expectations

  • Run Spotless formatting for changed files.
  • Resolve SonarQube issues in touched code; do not introduce new blocker/critical issues.
  • For large DB-backed results, prefer pagination/streaming/projections and avoid unbounded in-memory collections.
  • For PostgreSQL DAO queries that span multiple datasets or act on multiple tables, prefer CTEs (WITH) when they simplify logic and reduce repeated work.
  • Favor Java records for new immutable DTO/view models when framework/persistence mapping allows.

Testing and Test Data

  • Add or update tests for behavior changes in src/test/java.
  • Use synthetic test data only; do not include real or realistic PII, tokens, or secrets.
  • Do not use Mockito lenient stubbing (lenient()); prefer strict stubbing and remove unused/mismatched stubs.

Source of Truth

  • docs/API_GUIDELINES.md
  • docs/ARCHITECTURE.md
  • docs/ONBOARDING.md
  • docs/ai/prompts/
  • CONTRIBUTING.md
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.

  1. 2d ago First seen · 43 lines · 420 tokens per session scan A 4a4a3a303044

Subscribe to this mod's changes

consent copilot-instructions.md is an instructions file published in the GitHub repository DataBiosphere/consent (11 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 420 tokens to every session, about $0.0021 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.

Related

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens

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.

langchain-ai/langchain · 4,345 tokens