Borrowing it
Nothing to install: this file belongs to Garudex-Labs/caracal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Garudex-Labs/caracal/main/.github/instructions/delivery-architecture.instructions.mdgit clone --depth 1 https://github.com/Garudex-Labs/caracalWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/garudex-labs/caracal/delivery-architecture)<a href="https://agentmods.dev/instructions/garudex-labs/caracal/delivery-architecture"><img src="https://agentmods.dev/badge/instructions/garudex-labs/caracal/delivery-architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/garudex-labs/caracal/delivery-architecture"><img src="https://agentmods.dev/badge/instructions/garudex-labs/caracal/delivery-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00260 | $0.00260 |
| Opus 5 | $0.00130 | $0.00130 |
| Sonnet 5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
caracal delivery-architecture.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 10d 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.
What it actually says
Delivery And Architecture
- Separate development and production behavior through explicit configuration, build targets, secrets handling, and deployment paths.
- Must not mix development tooling, debug behavior, mock integrations, or test-only dependencies into production artifacts or runtime paths.
- Use feature flags for incomplete, risky, or staged functionality so rollout and rollback stay controlled without branching the codebase.
- Keep feature flag evaluation, defaults, and lifecycle management centralized instead of scattering ad hoc checks through the codebase.
- Centralize shared components such as configuration, error models, utilities, and cross-cutting helpers within a single approved layer per product.
- Must not duplicate shared logic across packages, apps, or services when a current in-product shared layer already owns that concern.
- Keep packaging, deployment, and distribution flows reproducible, minimal, and automation-friendly.
- Choose designs that improve security, performance, and maintainability without adding unnecessary steps, tools, or local setup burden to the developer workflow.
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.
- 10d ago First seen · 15 lines · 260 tokens per session scan A 8b7389b7914f
caracal delivery-architecture.instructions.md is an instructions file published in the GitHub repository Garudex-Labs/caracal (206 stars, last pushed 3d ago), licensed Apache-2.0. It adds 260 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.
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).
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.