agentmods.dev

consent AGENTS.md

A repository guide for DataBiosphere/consent that tells coding agents and GitHub Copilot where to find project rules, architecture notes, and development guidance.

In plain words
What is it for?
Use it when adding or changing API routes, implementing features, fixing bugs, refactoring code, writing tests, or preparing implementation plans in this repository.
Why use it?
It reduces the need to search through scattered documentation and helps keep changes consistent with the repository’s design, security, API, testing, and data rules.

Instructions file for CodexOpenCode

11 4d ago A scan 263 tokens original BSD-3-Clause
View the source file DataBiosphere/consent
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/agents-md
Clone the repo
git clone --depth 1 https://github.com/DataBiosphere/consent

Made for: Codex, OpenCode.

Per session 263 This file is loaded in full into every session.
When invoked 263 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.00263 $0.00263
Opus 5 $0.00131 $0.00131
Sonnet 5 $0.00053 $0.00053
Haiku 4.5 $0.00026 $0.00026

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

Security

Grade A, and why

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

AGENTS.md · 31 lines

What it actually says

Agent Guidance Index

This repository uses multiple instruction entry points.

For GitHub Copilot (GitHub UI / PR review)

  • Primary file: .github/copilot-instructions.md

For Repo Conventions and Implementation Details

  • docs/API_GUIDELINES.md
  • docs/ARCHITECTURE.md
  • docs/ONBOARDING.md
  • docs/plans/README.md
  • docs/ai/prompts/README.md
  • docs/ai/prompts/api-endpoint.md
  • docs/ai/prompts/feature-development.md
  • docs/ai/prompts/bugfix.md
  • docs/ai/prompts/refactor.md
  • CONTRIBUTING.md

Key Rules (Quick Reference)

  • Keep Resource -> Service -> DAO layering.
  • /api routes are authenticated (proxy/OAUTH-decorated); non-/api routes are unauthenticated.
  • Update src/main/resources/assets/api-docs.yaml when API contracts change.
  • Add/update tests for behavior changes.
  • Put new implementation plans and migration design docs under docs/plans/.
  • Avoid Mockito lenient stubbing (lenient()); keep tests strict-stubbing compliant.
  • Use synthetic test data only.
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 · 31 lines · 263 tokens per session scan A fda5a3fcc01b

Subscribe to this mod's changes

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

Code reviewDebuggingTesting
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