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/console-example-naming.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/console-example-naming)<a href="https://agentmods.dev/instructions/garudex-labs/caracal/console-example-naming"><img src="https://agentmods.dev/badge/instructions/garudex-labs/caracal/console-example-naming.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.00682 | $0.00682 |
| Opus 5 | $0.00341 | $0.00341 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
caracal console-example-naming.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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Console Example Naming
- Applies to web-console-facing help, info pages, tooltips, field examples, guided setup copy, placeholder examples, and tests that assert those strings.
- Use the approved naming universe when example, demo, placeholder, or reference data is needed.
- Keep names contextually appropriate, realistic, operational, and internally consistent.
- Do not introduce random placeholder names such as
payments-api,payments-worker,alice,bob,Acme, generic GitHub examples, or unrelated fake brands.
Approved Naming Universe
- Person names: Richard Hendricks, Bertram Gilfoyle, Erlich Bachman, Jian Yang, Peter Gregory, Gavin Belson, Monica Hall, Laurie Bream.
- AI names: Anton, Fiona, PiperNet AI.
- Company names: Pied Piper, Hooli, Raviga Capital, Endframe.
- Product names: Nucleus, PiperChat, Not Hotdog, HooliBox, PiperNet.
Contextual Defaults
- Application or agent names: Anton, Fiona, PiperNet AI.
- Zone names: Pied Piper Production, Hooli Staging, Raviga Capital Sandbox.
- Resource names: PiperNet, Not Hotdog, PiperChat, HooliBox, Nucleus.
- Resource identifiers:
resource://pipernet,resource://not-hotdog,resource://piperchat,resource://hoolibox,resource://nucleus. - Provider names: Hooli OIDC, Hooli PiperNet OIDC, Raviga Capital OAuth.
- User or subject examples: Richard Hendricks, Monica Hall,
user:[email protected]. - Policy examples: allow PiperNet read for Pied Piper operators; PiperNet baseline v3.
- File/path examples:
/home/richard/pied-piper/policies/pipernet.rego,~/.config/caracal/anton-client-secret. - Environment variable examples:
CARACAL_RESOURCE_PIPERNET_TOKEN.
Writing Rules
- Prefer human-readable names in explanatory UI copy.
- Use numeric or typed examples for numeric, duration, boolean, URL, identifier, path, JSON, and enum fields; do not substitute names from the approved universe when the field is not a name-like value.
- Prefer slugged identifiers only where the backend/API value is specifically being illustrated.
- Match the entity type: use an AI name for an Application/agent, a product name for a Resource, a company name for a Zone or organization-like boundary, and a person name for a user/session subject.
- Use reserved example domains only when a URL is required, with the approved brand in the host, such as
https://api.pipernet.exampleorhttps://login.hooli.example/oauth/token. - Do not use generic help boilerplate such as "Use this when the form needs a concrete value before it can continue" or "supplies the value used by the current workflow"; explain the field's operational purpose and downstream impact.
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.
- 7d ago First seen · 40 lines · 682 tokens per session scan A 69c4b8857c3b
caracal console-example-naming.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 682 tokens to every session, about $0.0034 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.