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/devkade/pi-opentelemetry/agents-mdgit clone --depth 1 https://github.com/devkade/pi-opentelemetryWhat 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 | $0.00236 | $0.00236 |
| Opus 5 | $0.00118 | $0.00118 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
pi-opentelemetry 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 2d 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
pi-opentelemetry
Pi usage observability extension project.
Essentials
- Observability scope must include Trace + Metrics + Diagnostics.
- The default privacy profile is detailed-with-redaction.
- Collect detailed payloads, but sensitive-data masking is mandatory.
- Keep metrics low-cardinality, and record rich context primarily in traces.
- Keep operational diagnostics commands (
/otel-status,/otel-open-trace) as baseline functionality. - Before starting work, check
PLAN.mdthenPROGRESS.mdto understand the current goal/owner/blocker/next action.
Documents
- Work plan/status: PLAN.md, PROGRESS.md
- Documentation index: docs/index.md
- OTel architecture/event mapping: docs/otel-architecture.md
- Privacy/redaction policy: docs/privacy-redaction.md
- Operations/diagnostics guide: docs/operations.md
- Documentation governance standard: docs/metadoc.md
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.
- 2d ago First seen · 22 lines · 236 tokens per session scan A 2bddb055c9f3
pi-opentelemetry AGENTS.md is an instructions file published in the GitHub repository devkade/pi-opentelemetry (5 stars, last pushed 6mo ago), licensed MIT. It adds 236 tokens to every session, about $0.0012 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-31.
Other instructions, from other repositories
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.