Borrowing it
Nothing to install: this file belongs to lukacf/meerkat. 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/lukacf/meerkat/main/AGENTS.mdgit clone --depth 1 https://github.com/lukacf/meerkatWrote 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/lukacf/meerkat/agents-md)<a href="https://agentmods.dev/instructions/lukacf/meerkat/agents-md"><img src="https://agentmods.dev/badge/instructions/lukacf/meerkat/agents-md/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/lukacf/meerkat/agents-md"><img src="https://agentmods.dev/badge/instructions/lukacf/meerkat/agents-md.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.00482 | $0.00482 |
| Opus 5.5 | $0.00193 | $0.00193 |
| Sonnet 5.5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
meerkat AGENTS.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 1mo 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
AGENTS.md
This repository uses Make as the developer-facing command surface.
Cargo is the default backend:
make build
make check
make lint
make test
make agent-gate
BuildBuddy is opt-in. When the machine has BuildBuddy access, the same broad local lanes can run through the macOS arm64 Bazel/RBE path:
MEERKAT_BUILDBUDDY=1 make build
MEERKAT_BUILDBUDDY=1 make check
MEERKAT_BUILDBUDDY=1 make lint
MEERKAT_BUILDBUDDY=1 make test
MEERKAT_BUILDBUDDY=1 make e2e-fast
MEERKAT_BUILDBUDDY=1 make e2e-system
MEERKAT_BUILDBUDDY=1 make e2e-live
MEERKAT_BUILDBUDDY=1 make e2e-smoke
Explicit BuildBuddy targets are available when you do not want environment
switching: make buildbuddy-build, make buildbuddy-check,
make buildbuddy-clippy, make buildbuddy-test, make buildbuddy-test-unit,
make buildbuddy-test-int, make buildbuddy-e2e-fast, and
make buildbuddy-e2e-system. Live-provider lanes are available as
make buildbuddy-e2e-live and make buildbuddy-e2e-smoke when provider keys
are configured.
Run make buildbuddy-doctor when BuildBuddy setup looks suspicious. It checks
the API key, pinned bb CLI, generated Bazel files, selector behavior, and lane
isolation without printing secrets. Use BUILDBUDDY_DRY_RUN=1 with explicit
BuildBuddy Make targets to inspect the selected command without running it.
For same-checkout multi-agent work, set a distinct RUST_LANE_ID per agent if
you want stable warm local output roots. Separate Git worktrees are already
isolated by path hash.
Avoid raw cargo and raw bb for normal repo work. Use ./scripts/repo-cargo
for targeted Cargo commands and scripts/buildbuddy-dev only when extending or
debugging the BuildBuddy local facade.
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.
- 1mo ago First seen · 49 lines · 482 tokens per session scan A 5fbebba1d4ac
meerkat AGENTS.md is an instructions file published in the GitHub repository lukacf/meerkat (23 stars, last pushed today), licensed Apache-2.0. It adds 482 tokens to every session, about $0.0019 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.