Apache SkyWalking BanyanDB is a database for collecting, analyzing, and storing metrics, traces, and logs produced by observability and application-performance systems. It is intended for platforms such as Apache SkyWalking that need to work with monitoring data.
Borrowing it
Nothing to install: this file belongs to apache/skywalking-banyandb. 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/apache/skywalking-banyandb/main/AGENTS.mdgit clone --depth 1 https://github.com/apache/skywalking-banyandbWrote 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/apache/skywalking-banyandb/agents-md)<a href="https://agentmods.dev/instructions/apache/skywalking-banyandb/agents-md"><img src="https://agentmods.dev/badge/instructions/apache/skywalking-banyandb/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/apache/skywalking-banyandb/agents-md"><img src="https://agentmods.dev/badge/instructions/apache/skywalking-banyandb/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.00432 | $0.00432 |
| Opus 5.5 | $0.00173 | $0.00173 |
| Sonnet 5.5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
skywalking-banyandb 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.
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.
BanyanDB Agent Guide
BanyanDB is a distributed time-series database written in Go. Follow nearby code and tests; keep changes focused on the requested behavior.
Completion and scope
- Finish the requested change and relevant verification without asking about routine next steps. Stop when the requested outcome is verified or a concrete blocker requires user input; do not expand into unrelated fixes or redesigns.
- Preserve unrelated working-tree changes. Do not commit, push, publish, or change external resources unless requested or already authorized.
- Use independent subagents when their work saves time; small tasks do not need delegation or a separate review workflow.
Go conventions
.golangci.ymlis authoritative for lint rules, protobuf import aliases, exclusions, and the 170-character line limit..golangci-format.ymlcontrols formatting with gci and gofumpt; its exclusions are not general lint exclusions.- Import groups: standard library, third-party packages, then this repository.
- Avoid shadowing existing variables. Short names and
if err := ...are valid when they do not shadow another variable; use descriptive names where useful. - Check errors and add meaningful context with
%wwhen wrapping. Preserve error identity and the relevant API's error-handling conventions. - Document exported functions and types with concise, punctuated comments. Add implementation comments only for non-obvious logic.
Correctness and validation
- Follow existing test conventions and run the smallest relevant suites first. Expand validation for affected integration boundaries, generated code, or shared infrastructure; avoid unrelated full builds during read-only or wording tasks.
- Preserve persisted-data and wire compatibility. For format, schema, or protocol changes, check existing data and mixed-version behavior as applicable.
- For concurrent or stateful changes, consider cancellation, resource ownership, bounded memory, and recovery. Use the repository's established helpers.
- Read design documents only for the subsystem or contract being changed. Follow
any more-specific
AGENTS.mdin the affected directory.
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 Changed · -247 lines · -1,818 tokens per session 80bf1b3c9432
- 1mo ago First seen · 287 lines · 2,250 tokens per session scan A a4e0c8e8887f
skywalking-banyandb AGENTS.md is an instructions file published in the GitHub repository apache/skywalking-banyandb (354 stars, last pushed today), licensed Apache-2.0. It adds 432 tokens to every session, about $0.0017 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-09-03.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.