Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/consensys/ask-o11y-plugin/claude-mdgit clone --depth 1 https://github.com/Consensys/ask-o11y-pluginWrote 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/consensys/ask-o11y-plugin/claude-md)<a href="https://agentmods.dev/instructions/consensys/ask-o11y-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/consensys/ask-o11y-plugin/claude-md.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.03967 | $0.03967 |
| Opus 5 | $0.01983 | $0.01983 |
| Sonnet 5 | $0.00793 | $0.00793 |
| Haiku 4.5 | $0.00397 | $0.00397 |
Grade A, and why
ask-o11y-plugin CLAUDE.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 6d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Overview
Ask O11y is a Grafana app plugin providing AI-powered observability assistance via natural language. Users query metrics, logs, traces, and manage dashboards without writing PromQL/LogQL.
Stack: TypeScript/React 18 (strict) + Go 1.21+ monorepo with YAML infrastructure configs. Key technologies: Grafana plugin SDK, Tailwind CSS, MCP protocol, Kubernetes/ArgoCD deployments, Redis, Tempo, Loki, Mimir. Always run lint and tests before considering a task complete.
Architecture: Server-side agentic loop (Go) streams SSE to React frontend. MCP proxy aggregates multiple tool servers. RBAC enforced at tool listing and execution via ToolAnnotations.
Exploration & Investigation Rules
When asked to explore a codebase or investigate an issue, limit initial exploration to 3-5 targeted file reads before proposing a plan. Do NOT do exhaustive grep/search loops. If you haven't found what you need in 5 minutes of exploration, stop and ask the user for direction.
Commands
Always chain with nvm use 22 && — shell state doesn't persist between Bash calls.
nvm use 22 && npm run server # Start dev environment (Docker)
nvm use 22 && npm run server:full # Multi-org dev environment
nvm use 22 && npm run build # Full production build
nvm use 22 && npm run build:backend # Backend only (current platform)
nvm use 22 && npm run test:ci # Frontend unit tests
nvm use 22 && npm run lint # Linting
nvm use 22 && npm run typecheck # Type checking
nvm use 22 && npm run validate:openapi # OpenAPI spec validation
nvm use 22 && npm run validate # Full Grafana plugin validator (build + archive + run)
nvm use 22 && npm run validate:clean # Remove validator zip artifacts
nvm use 22 && npm run e2e # Playwright E2E tests
go test ./pkg/... # Backend tests
docker compose restart grafana # Reload after backend rebuild
Quality Gates (after every code change)
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.
- 6d ago First seen · 256 lines · 3,967 tokens per session scan A 18fe8d5a9eef
ask-o11y-plugin CLAUDE.md is an instructions file published in the GitHub repository Consensys/ask-o11y-plugin (40 stars, last pushed yesterday), licensed MIT. It adds 3,967 tokens to every session, about $0.0198 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
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).
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 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.
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.