agentmods.dev

semanticworkbench CLAUDE.md

Developer instructions for Microsoft Semantic Workbench, a project for building AI assistants and related libraries.

In plain words
What is it for?
They help organize generated documentation about libraries and assistants and provide project commands and coding guidance.
Why use it?
They give contributors shared guidance for understanding the codebase, generating context files, and following its development conventions.

Instructions file

407 5mo ago A scan 1,145 tokens original MIT
View the source file microsoft/semanticworkbench
Install

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.

agentmods
npx agentmods add instructions/microsoft/semanticworkbench/claude-md
Clone the repo
git clone --depth 1 https://github.com/microsoft/semanticworkbench
Per session 1,145 This file is loaded in full into every session.
When invoked 1,145 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01145 $0.01145
Opus 5 $0.00573 $0.00573
Sonnet 5 $0.00229 $0.00229
Haiku 4.5 $0.00114 $0.00114

Measured 2d ago against content hash fb6769fe9233, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

semanticworkbench 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 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.

CLAUDE.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Semantic Workbench Developer Guidelines

AI Context System

Generate comprehensive codebase context for development:

  • make ai-context-files - Generate AI context files for all components
  • Files created in ai_context/generated/ organized by logical boundaries:
    • Python Libraries (by functional group):
      • PYTHON_LIBRARIES_CORE.md - Core API model, assistant framework, events
      • PYTHON_LIBRARIES_AI_CLIENTS.md - Anthropic, OpenAI, LLM clients
      • PYTHON_LIBRARIES_EXTENSIONS.md - Assistant/MCP extensions, content safety
      • PYTHON_LIBRARIES_SPECIALIZED.md - Guided conversation, assistant drive
      • PYTHON_LIBRARIES_SKILLS.md - Skills library with patterns and routines
    • Assistants (by individual implementation):
      • ASSISTANTS_OVERVIEW.md - Common patterns and all assistant summaries
      • ASSISTANT_PROJECT.md - Project assistant (most complex)
      • ASSISTANT_DOCUMENT.md - Document processing assistant
      • ASSISTANT_CODESPACE.md - Development environment assistant
      • ASSISTANT_NAVIGATOR.md - Workbench navigation assistant
      • ASSISTANT_PROSPECTOR.md - Advanced agent with artifact creation
      • ASSISTANTS_OTHER.md - Explorer, guided conversation, skill assistants
    • Platform Components:
      • WORKBENCH_FRONTEND.md - React app components and UI patterns
      • WORKBENCH_SERVICE.md - Backend API, database, and service logic
      • MCP_SERVERS.md - Model Context Protocol server implementations
      • DOTNET_LIBRARIES.md - .NET libraries and connectors
    • Supporting Files:
      • EXAMPLES.md - Sample code and getting-started templates
      • TOOLS.md - Build scripts and development utilities
      • CONFIGURATION.md - Root-level configs and project setup
      • ASPIRE_ORCHESTRATOR.md - Container orchestration setup

Using AI Context for Development:

  • New developers: Read CONFIGURATION.md + PYTHON_LIBRARIES_CORE.md for project overview
  • Building assistants:
    • Start with ASSISTANTS_OVERVIEW.md for common patterns
    • Use specific assistant files (e.g., ASSISTANT_PROJECT.md) as implementation templates
  • Working on specific assistants: Load the relevant ASSISTANT_*.md file for focused context
  • Library development: Choose appropriate PYTHON_LIBRARIES_*.md file by functional area
  • Frontend work: Study component patterns in WORKBENCH_FRONTEND.md
  • API development: Follow service patterns from WORKBENCH_SERVICE.md
  • MCP servers: Use existing servers in MCP_SERVERS.md as templates
  • AI tools: Provide relevant context files for better code generation and debugging
  • Code reviews: Reference context files to understand cross-component impacts

Read the full file on GitHub · 83 lines

Changes

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.

  1. 2d ago First seen · 83 lines · 1,145 tokens per session scan A fb6769fe9233

Subscribe to this mod's changes

semanticworkbench CLAUDE.md is an instructions file published in the GitHub repository microsoft/semanticworkbench (407 stars, last pushed 5mo ago), licensed MIT. It adds 1,145 tokens to every session, about $0.0057 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.

Related

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.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens