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/secprog/dependency-track-mcp/claude-mdgit clone --depth 1 https://github.com/secprog/dependency-track-mcpWrote 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/secprog/dependency-track-mcp/claude-md)<a href="https://agentmods.dev/instructions/secprog/dependency-track-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/secprog/dependency-track-mcp/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.00780 | $0.00780 |
| Opus 5 | $0.00390 | $0.00390 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
dependency-track-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 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 — 96 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
Dependency Track MCP Server - A Model Context Protocol (MCP) server enabling AI assistants to interact with OWASP Dependency Track for software composition analysis. Python 3.10+, uses FastMCP framework.
Commands
# Install dependencies
pip install -e ".[dev]"
# Run tests
pytest # All tests
pytest -m unit # Unit tests only
pytest -m integration # Integration tests only
pytest tests/test_client.py # Single test file
pytest -k "test_name" # Run tests matching pattern
# Linting and formatting
ruff check . # Check code style
ruff check . --fix # Auto-fix issues
ruff format . # Format code
# Run the server
dependency-track-mcp # Uses entry point
python -m dependency_track_mcp.main # Direct module execution
Architecture
Layered Design
Client (with Bearer token)
↓
Main Server (main.py) - validates JWT via JWKS
↓
FastMCP Server (server.py) - registers tools
↓
Tool Handlers (tools/*.py) - call client methods
↓
DependencyTrackClient (client.py) [singleton] - async HTTP
↓
Dependency Track API
Key Modules
- main.py: Main entry point with OAuth 2.1 authentication, FastAPI, JWT validation via JWKS
- server.py: FastMCP server initialization, registers tools
- client.py: Async HTTP client with singleton pattern, retry logic, rate limit handling
- config.py: Pydantic settings from environment variables (MCP_ and DEPENDENCY_TRACK_ prefixes), validates security requirements
- oauth.py: JWT validation, scope-based authorization middleware, JWKS caching
- scopes.py: Defines 9 MCP scopes for fine-grained access control
- models.py: Pydantic models for API types (Project, Component, Vulnerability, Finding, etc.)
- exceptions.py: Custom exception hierarchy mapping to HTTP status codes
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 · 96 lines · 780 tokens per session scan A d699e374fde8
dependency-track-mcp CLAUDE.md is an instructions file published in the GitHub repository secprog/dependency-track-mcp (5 stars, last pushed 20d ago), licensed MIT. It adds 780 tokens to every session, about $0.0039 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
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).