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/nokia/mcp-redfish/copilot-instructionsgit clone --depth 1 https://github.com/nokia/mcp-redfishWrote 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/nokia/mcp-redfish/copilot-instructions)<a href="https://agentmods.dev/instructions/nokia/mcp-redfish/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/nokia/mcp-redfish/copilot-instructions.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.01874 | $0.01874 |
| Opus 5 | $0.00937 | $0.00937 |
| Sonnet 5 | $0.00375 | $0.00375 |
| Haiku 4.5 | $0.00187 | $0.00187 |
Grade A, and why
mcp-redfish copilot-instructions.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 today.
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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for MCP Redfish Server
Project Architecture
This is a FastMCP-based Model Context Protocol (MCP) server that provides a natural language interface to Redfish-enabled infrastructure. The architecture follows a layered design:
src/main.py: Entry point withRedfishMCPServerclass handling SSDP discovery and server startupsrc/common/server.py: FastMCP instance initialization (mcp = FastMCP("Redfish MCP Server", auth=...))src/common/auth.py: MapsMCP_AUTH_*to FastMCP token verifierssrc/common/validation.py: Fail-closed HTTP auth, bind, and TLS rulessrc/tools/: MCP tool implementations using@mcp.tool()decorators (auto-registered via imports)src/common/client.py: Redfish client wrapper with retry logic usingtenacitylibrarysrc/common/discovery.py: SSDP discovery for automatic Redfish endpoint detection
Tool Registration Pattern: Tools are auto-registered by importing modules in src/tools/__init__.py. Each tool uses @mcp.tool() decorator from the global mcp instance.
Key Development Patterns
MCP Tool Development
from ..common.server import mcp
@mcp.tool()
async def tool_name(param: str) -> dict:
"""Tool description for AI agents."""
# Implementation
Configuration Hierarchy
- Environment variables (
.envfile recommended) - Per-host overrides in
REDFISH_HOSTSJSON array - Global defaults from
src/common/config.py
Critical: Set test environment variables BEFORE importing src modules in tests (see test/conftest.py).
Redfish Client Usage
from ..common.client import RedfishClient
from .. import common
# Get server config, create client, handle cleanup
server_cfg = common.hosts.get_hosts()[0]
client = RedfishClient(server_cfg, common.config)
try:
response = client.get("/redfish/v1/Systems")
finally:
client.logout() # Always cleanup
Development Workflow
Supported runtimes: Python 3.14 recommended; Python 3.13 deprecated (policy).
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.
- today Changed · +18 lines · +474 tokens per session 8147763afe18
- 4d ago First seen · 155 lines · 1,400 tokens per session scan A 69fd9c30fbf0
mcp-redfish copilot-instructions.md is an instructions file published in the GitHub repository nokia/mcp-redfish (19 stars, last pushed today), licensed BSD-3-Clause. It adds 1,874 tokens to every session, about $0.0094 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
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.