AgenticAI backend.instructions.md

A set of guidelines for building backend services, including APIs, database access, validation, authentication, and error handling.

In plain words
What is it for?
Use it when creating or reviewing REST APIs, database code, input validation, login systems, permissions, and backend error handling.
Why use it?
It gives coding agents consistent rules for common backend decisions, such as HTTP methods, safe database queries, and standard error responses.

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/marcelroozekrans/agenticai/backend
Clone the repo
git clone --depth 1 https://github.com/MarcelRoozekrans/AgenticAI

Made for: GitHub Copilot.

Per session 424 This file is loaded in full into every session.
When invoked 424 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.00424 $0.00424
Opus 5 $0.00212 $0.00212
Sonnet 5 $0.00085 $0.00085
Haiku 4.5 $0.00042 $0.00042

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

Security

Grade A, and why

AgenticAI backend.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/instructions/backend.instructions.md · 86 lines

What it actually says

Backend Development Guidelines

API Design

RESTful Principles

  • Use proper HTTP methods (GET, POST, PUT, PATCH, DELETE)
  • Return appropriate status codes
  • Use plural nouns for resource endpoints
  • Version your APIs (e.g., /api/v1/)
  • Implement pagination for list endpoints

Response Format

{
  "data": {},
  "meta": {
    "timestamp": "ISO8601",
    "requestId": "uuid"
  },
  "errors": []
}

Database Operations

Query Best Practices

  • Use parameterized queries (prevent SQL injection)
  • Implement proper indexing
  • Use transactions for multi-step operations
  • Optimize N+1 query problems
  • Use connection pooling

Data Validation

  • Validate all inputs at the API boundary
  • Use schema validation libraries
  • Sanitize data before storage
  • Implement rate limiting

Authentication & Authorization

  • Use industry-standard protocols (OAuth2, JWT)
  • Implement proper token refresh mechanisms
  • Use secure password hashing (bcrypt, argon2)
  • Apply principle of least privilege
  • Log authentication events

Error Handling

Error Response Format

{
  "error": {
    "code": "ERROR_CODE",
    "message": "Human readable message",
    "details": {}
  }
}

Logging

  • Log all errors with stack traces
  • Include request context (user, request ID)
  • Use structured logging (JSON format)
  • Don't log sensitive data (passwords, tokens)

Performance

  • Implement caching strategies (Redis, in-memory)
  • Use async operations where appropriate
  • Optimize database queries
  • Implement connection pooling
  • Monitor and set up alerts

Testing

  • Write unit tests for business logic
  • Write integration tests for API endpoints
  • Use mocking for external dependencies
  • Test error scenarios and edge cases
  • Maintain test data factories
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 · 86 lines · 424 tokens per session scan A bfcf611e0492

Subscribe to this mod's changes

AgenticAI backend.instructions.md is an instructions file published in the GitHub repository MarcelRoozekrans/AgenticAI (1 stars, last pushed 4mo ago), licensed MIT. It adds 424 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-31.

Related

Other instructions, from other repositories

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

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

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

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

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

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