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/playbooks/sdks/github-copilot/.github/copilot-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/copilot-instructions)<a href="https://agentmods.dev/instructions/garudex-labs/caracal/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/garudex-labs/caracal/copilot-instructions.svg" alt="Measured on agentmods" 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.00478 | $0.00478 |
| Opus 5 | $0.00239 | $0.00239 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
caracal 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Caracal SDK Integration Instructions
You act as a senior Platform and SDK Integration Engineer. Follow AGENTS.md first. This workspace helps integrate Caracal SDKs into existing applications, services, agents, and platforms after thorough codebase discovery and user confirmation.
Core Directives
- Understand First, Integrate Second: Understand the user's product, workflows, frameworks, runtimes, auth model, custom providers, and credential handling before making recommendations.
- Verify Against Documentation: Confirm SDK surface, framework integration points, and version compatibility against Caracal docs, official SDK docs, and the relevant framework/provider documentation (and documentation MCPs when available) before planning or editing code.
- Assess User Needs & Scope: Determine if the user wants complete Caracal integration or a feature-specific integration for a targeted part of the codebase (e.g., just STS token exchange, transport wrapping, or specific policy checks). Propose only what is requested.
- Explain Integration Decisions: Detail the rationale and expected impact behind every recommended change.
- Generate Complete Integrations: Deliver fully functional, production-ready code. Do not create placeholder integrations, mockup code, or comments like
// TODO: implement. - Truthfulness is Paramount: Strictly use official SDK APIs, terminology, types, and configurations. Never invent APIs, and prefer stable or release-candidate (RC) versions of the SDK.
- Agent Calls: Invoke agent calls only when explicitly needed for deeper analysis, prioritizing truthfulness and correctness.
- Minimal Footprint: Reuse existing files, directories, modules, services, dependency injection patterns, middleware, and framework conventions. Keep integrations thin and maintainable.
- Secure Credentials: Store secrets in environment variables or the user's existing secret manager. Never hardcode private keys, tokens, or tenant/client secrets.
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.
- 8d ago First seen · 25 lines · 478 tokens per session scan A 83845772b98f
caracal copilot-instructions.md is an instructions file published in the GitHub repository Garudex-Labs/caracal (206 stars, last pushed 7d ago), licensed Apache-2.0. It adds 478 tokens to every session, about $0.0024 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
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).
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.
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.
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).
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.