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/trendmicro/vision-one-mcp-server/claude-mdgit clone --depth 1 https://github.com/trendmicro/vision-one-mcp-serverWrote 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/trendmicro/vision-one-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/trendmicro/vision-one-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/trendmicro/vision-one-mcp-server/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.01668 | $0.01668 |
| Opus 5 | $0.00834 | $0.00834 |
| Sonnet 5 | $0.00334 | $0.00334 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade A, and why
vision-one-mcp-server 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 5d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Trend Vision One MCP Server - A Go-based Model Context Protocol (MCP) server that bridges AI tooling (Claude, VSCode + GitHub Copilot) with Trend Vision One security platform APIs. Enables natural language interaction with security services like Workbench alerts, Cloud Posture, endpoint management, attack surface discovery, and AI security guardrails.
Build & Test Commands
# Build
make mcpserver # Build to ./bin/v1-mcp-server
go build -o ./bin/v1-mcp-server ./cmd/v1-mcp-server/main.go
# Test
go test -v ./... # Run all tests
# Lint & Format
./script/check-gofmt # Check formatting
./script/lint # Run golangci-lint
gofmt -s -w ./ # Auto-format code
# Run locally
./bin/v1-mcp-server -region us # Requires TREND_VISION_ONE_API_KEY env var
Architecture
cmd/v1-mcp-server/main.go # Entry point, CLI flags, region validation
internal/v1mcp/server.go # MCP server setup, tool registration
internal/v1mcp/tools/*.go # Tool handlers (one file per domain)
internal/v1client/*.go # HTTP client, API endpoint methods
Request Flow: MCP Request → Tool Handler → Parameter Extraction → v1client API call → HTTP → Response → MCP Result
Key Conventions
Tool Implementation Pattern
Each tool is a factory function returning mcpserver.ServerTool:
func toolDomainResourceAction(client *v1client.V1ApiClient) mcpserver.ServerTool {
return mcpserver.ServerTool{
Tool: mcp.NewTool("domain_resource_action",
mcp.WithDescription("..."),
mcp.WithString("param", mcp.Description("...")),
mcp.WithToolAnnotation(mcp.ToolAnnotation{ReadOnlyHint: toPtr(true)}),
),
Handler: func(ctx context.Context, request mcp.CallToolRequest) (*mcp.CallToolResult, error) {
// Extract parameters, call API, return result
},
}
}
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.
- 5d ago First seen · 149 lines · 1,668 tokens per session scan A 47d7a2ff06ce
vision-one-mcp-server CLAUDE.md is an instructions file published in the GitHub repository trendmicro/vision-one-mcp-server (38 stars, last pushed 4mo ago), licensed MIT. It adds 1,668 tokens to every session, about $0.0083 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
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 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.
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.
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).