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/owretch/zed-extension-bicep/agents-mdgit clone --depth 1 https://github.com/oWretch/zed-extension-bicepWrote 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/owretch/zed-extension-bicep/agents-md)<a href="https://agentmods.dev/instructions/owretch/zed-extension-bicep/agents-md"><img src="https://agentmods.dev/badge/instructions/owretch/zed-extension-bicep/agents-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 | $0.02388 | $0.02388 |
| Opus 5 | $0.01194 | $0.01194 |
| Sonnet 5 | $0.00478 | $0.00478 |
| Haiku 4.5 | $0.00239 | $0.00239 |
Grade A, and why
zed-extension-bicep 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 4d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Coding Agent Guide
Project Overview
This is a Zed editor extension that adds Bicep language support — syntax highlighting, IntelliSense, and error checking for both .bicep and .bicepparam files.
The extension is written in Rust, compiled to WebAssembly (wasm32-wasip2), and uses the zed_extension_api crate. At runtime it downloads the official Bicep Language Server and launches it via the .NET runtime.
Architecture
zed-extension-bicep/
├── src/
│ └── bicep.rs # Extension entry point (Rust → WASM)
├── extension.toml # Zed extension metadata (name, version, grammars, LSP config)
├── Cargo.toml # Rust package manifest (version must match extension.toml)
├── languages/
│ ├── bicep/ # Language config for .bicep files
│ │ ├── config.toml # File associations, brackets, comments
│ │ ├── highlights.scm # Syntax highlighting queries (tree-sitter)
│ │ ├── indents.scm # Auto-indentation rules
│ │ ├── injections.scm # Language injection queries
│ │ ├── outline.scm # Symbol outline queries
│ │ └── brackets.scm # Bracket matching queries
│ └── bicep_params/ # Language config for .bicepparam files (same structure)
├── grammars/
│ └── bicep/ # Tree-sitter grammar for Bicep and Bicep Params (DO NOT HAND-EDIT src/)
├── .github/
│ └── workflows/
│ ├── release.yaml # Automated release via semantic-release
│ └── ci.yaml # PR checks (fmt, clippy, build)
├── .releaserc.json # semantic-release configuration
├── package.json # Node.js deps for semantic-release
├── scripts/
│ └── test-version-update.js # Validates version bump logic
├── docs/
│ └── SEMANTIC_RELEASE.md # Release process documentation
├── test.bicep # Sample Bicep file for manual testing
├── test.bicepparam # Sample Bicep params file for manual testing
└── bicepconfig.json # Bicep configuration for test files
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.
- 4d ago First seen · 219 lines · 2,388 tokens per session scan A 3c9e26e74b17
zed-extension-bicep AGENTS.md is an instructions file published in the GitHub repository oWretch/zed-extension-bicep (5 stars, last pushed 7d ago), licensed MIT. It adds 2,388 tokens to every session, about $0.0119 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
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).
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.
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.