opcua-mcp: Instructions file for Claude Code

CLAUDE.md

opcua-mcp CLAUDE.md is an instructions file for Claude Code from mwieczorkiewicz/opcua-mcp. It costs 9,660 tokens per session, scanned A, original, MIT.

A rule-driven workflow for software development that adapts its steps to the task and requires loading project-specific rule files and extensions.

In plain words
What is it for?
Use it when implementing software changes that must follow the project's rule details, validation steps, and file formats.
Why use it?
It gives the agent a consistent way to assess the work and apply the repository's required development rules.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Claude Code; mentions Codex; built for cline.

This is mwieczorkiewicz/opcua-mcp's own configuration. It tells Claude Code how to work on opcua-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything opcua-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mwieczorkiewicz/opcua-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mwieczorkiewicz/opcua-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/mwieczorkiewicz/opcua-mcp

Made for: Claude Code.

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

agentmods badge for opcua-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/mwieczorkiewicz/opcua-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/mwieczorkiewicz/opcua-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/mwieczorkiewicz/opcua-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/mwieczorkiewicz/opcua-mcp/claude-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.

agentmods 80×15 button for opcua-mcp CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/mwieczorkiewicz/opcua-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/mwieczorkiewicz/opcua-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9,660 This file is loaded in full into every session.
When invoked 9,660 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.09660 $0.09660
Opus 5 $0.04830 $0.04830
Sonnet 5 $0.01932 $0.01932
Haiku 4.5 $0.00966 $0.00966

Measured 12d ago against content hash 3d00daa05440, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

opcua-mcp 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 12d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

CLAUDE.md · 611 lines

How it starts

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

PRIORITY: This workflow OVERRIDES all other built-in workflows

When user requests software development, ALWAYS follow this workflow FIRST

Adaptive Workflow Principle

The workflow adapts to the work, not the other way around.

The AI model intelligently assesses what stages are needed based on:

  1. User's stated intent and clarity
  2. Existing codebase state (if any)
  3. Complexity and scope of change
  4. Risk and impact assessment

MANDATORY: Rule Details Loading

CRITICAL: When performing any phase, you MUST read and use relevant content from rule detail files. Check these paths in order and use the first one that exists, regardless of which IDE or setup method was used:

  • .aidlc/aidlc-rules/aws-aidlc-rule-details/ (typical with AI-assisted setup)
  • .aidlc-rule-details/ (typical with Cursor, Cline, Claude Code, GitHub Copilot, OpenAI Codex)
  • .kiro/aws-aidlc-rule-details/ (typical with Kiro IDE and CLI)
  • .amazonq/aws-aidlc-rule-details/ (typical with Amazon Q Developer)

All subsequent rule detail file references (e.g., common/process-overview.md, inception/workspace-detection.md) are relative to whichever rule details directory was resolved above.

Common Rules: ALWAYS load common rules at workflow start:

  • Load common/process-overview.md for workflow overview
  • Load common/session-continuity.md for session resumption guidance
  • Load common/content-validation.md for content validation requirements
  • Load common/question-format-guide.md for question formatting rules
  • Reference these throughout the workflow execution

MANDATORY: Extensions Loading (Context-Optimized)

CRITICAL: At workflow start, scan the extensions/ directory recursively but load ONLY lightweight opt-in files - NOT full rule files. Full rule files are loaded on-demand after the user opts in.

Loading process:

  1. List all subdirectories under extensions/ (e.g., extensions/security/, extensions/compliance/)
  2. In each subdirectory, load ONLY *.opt-in.md files - these contain the extension's opt-in prompt. The corresponding rules file is derived by convention: strip the .opt-in.md suffix and append .md (e.g., security-baseline.opt-in.mdsecurity-baseline.md)
  3. Do NOT load full rule files (e.g., security-baseline.md) at this stage

Read the full file on GitHub · 611 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. 12d ago First seen · 611 lines · 9,660 tokens per session scan A 3d00daa05440

Subscribe to this mod's changes

opcua-mcp CLAUDE.md is an instructions file published in the GitHub repository mwieczorkiewicz/opcua-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 9,660 tokens to every session, about $0.0483 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.

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,126 tokens

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.

vercel/next.js · 7,296 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,153 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

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,469 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