caracal: Instructions file for GitHub Copilot

.github/instructions/file-header.instructions.md

caracal file-header.instructions.md is an instructions file for GitHub Copilot from Garudex-Labs/caracal. It costs 249 tokens per session, scanned A, original, Apache-2.0.

A required copyright and description header for every source file. The header identifies Garudex Labs and Caracal, followed by one short sentence describing what the file is.

In plain words
What is it for?
Use it whenever creating or editing a source file, adapting the header to that file's programming-language comment syntax.
Why use it?
It keeps source-file ownership and purpose documented in a consistent format across the codebase.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is Garudex-Labs/caracal's own configuration. It tells GitHub Copilot how to work on caracal itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything caracal configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Garudex-Labs/caracal/main/.github/instructions/file-header.instructions.md
Clone the repo
git clone --depth 1 https://github.com/Garudex-Labs/caracal

Made for: GitHub Copilot.

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

agentmods badge for caracal file-header.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/garudex-labs/caracal/file-header.svg)](https://agentmods.dev/instructions/garudex-labs/caracal/file-header)
Your own site
<a href="https://agentmods.dev/instructions/garudex-labs/caracal/file-header"><img src="https://agentmods.dev/badge/instructions/garudex-labs/caracal/file-header.svg" alt="Measured on agentmods" height="20"></a>
Per session 249 This file is loaded in full into every session.
When invoked 249 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00249 $0.00249
Opus 5 $0.00125 $0.00125
Sonnet 5 $0.00050 $0.00050
Haiku 4.5 $0.00025 $0.00025

Measured 7d ago against content hash dc72d1b878a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

caracal file-header.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 7d 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/file-header.instructions.md · 29 lines

What it actually says

File Header

  • Applies to every source file in the codebase.

Required

  • Every source file must begin with this exact header (adapted to the file's comment syntax):
    Copyright (C) 2026 Garudex Labs.  All Rights Reserved.
    Caracal, a product of Garudex Labs
    
    {One short, clear one-line description of the file}
    
  • The description must be a single sentence: concise and direct.
  • Describe what the file is.
  • Preserve exact spacing: two spaces after All Rights Reserved.
  • Include the blank line between the copyright block and the description.
  • Adapt the comment syntax to match the file's language (e.g., """ for Python, // for JS/TS).

Forbidden

  • Must not omit the header from any source file.
  • Must not add metadata, version notes, or author lines inside the header block.
  • Must not add blank lines inside the copyright block itself.
  • Must not describe what was changed or why the file exists.
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. 7d ago First seen · 29 lines · 249 tokens per session scan A dc72d1b878a3

Subscribe to this mod's changes

caracal file-header.instructions.md is an instructions file published in the GitHub repository Garudex-Labs/caracal (205 stars, last pushed 6d ago), licensed Apache-2.0. It adds 249 tokens to every session, about $0.0012 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

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.

vercel/next.js · 7,296 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

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

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

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,469 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