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/filthyrake/damens_mcps/idrac-mcpgit clone --depth 1 https://github.com/filthyrake/damens_mcpsWrote 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/filthyrake/damens_mcps/idrac-mcp)<a href="https://agentmods.dev/instructions/filthyrake/damens_mcps/idrac-mcp"><img src="https://agentmods.dev/badge/instructions/filthyrake/damens_mcps/idrac-mcp.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.02471 | $0.02471 |
| Opus 5 | $0.01236 | $0.01236 |
| Sonnet 5 | $0.00494 | $0.00494 |
| Haiku 4.5 | $0.00247 | $0.00247 |
Grade B, and why
damens_mcps idrac-mcp.instructions.md scanned grade B with 1 finding 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Set permissions: `chmod 600 config.json` How it starts
The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path-Specific Instructions: iDRAC MCP Server
Path: idrac-mcp/
Project Overview
The iDRAC MCP server provides Dell PowerEdge server management capabilities through the Model Context Protocol. It allows AI assistants to manage Dell servers via iDRAC (Integrated Dell Remote Access Controller).
Key Characteristics
- Architecture: Pure JSON-RPC (no MCP library)
- Transport: stdin/stdout JSON-RPC protocol
- Canonical Server:
working_mcp_server.pyONLY - Configuration: JSON configuration file (
config.json) - Fleet Support: Manages multiple servers simultaneously
Critical Requirements
Server Implementation
- ONLY use
working_mcp_server.pyas the canonical implementation - DO NOT use or modify other server files (they exist for historical reasons)
- Server reads JSON-RPC from stdin, writes to stdout
- Use stderr for debugging:
print(message, file=sys.stderr) - Multiple server fleet support built-in
Power Operations
Power operations are extremely dangerous and can cause:
- Production downtime
- Data loss if systems aren't shut down gracefully
- Service interruption
- Hardware issues if done improperly
ALWAYS:
- Validate server IDs carefully
- Log all power operations with details
- Consider graceful shutdown before power off
- Implement confirmation for forced operations
- Check server status before operations
Dangerous Operations
These operations can cause significant problems:
- Power off/on/reset - Immediate downtime
- Force power off - Can cause data corruption
- BIOS configuration changes - Can brick servers
- Firmware updates - Can fail and brick hardware
Configuration
Configuration File Format
{
"servers": [
{
"id": "server-01",
"host": "192.168.1.10",
"username": "root",
"password": "calvin",
"verify_ssl": false
},
{
"id": "server-02",
"host": "192.168.1.11",
"username": "root",
"password": "calvin",
"verify_ssl": false
}
],
"defaults": {
"timeout": 30,
"retry_count": 3,
"retry_delay": 5
}
}
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.
- 4d ago First seen · 400 lines · 2,471 tokens per session scan B fe504721c2ba
damens_mcps idrac-mcp.instructions.md is an instructions file published in the GitHub repository filthyrake/damens_mcps (2 stars, last pushed 4d ago), licensed MIT. It adds 2,471 tokens to every session, about $0.0124 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
cml-mcp AGENTS.md
AGENTS.md instructions for xorrkaz/cml-mcp, covering agents.md — cml mcp server, project overview, compatibility goal, repository layout and tool modules (src/cmlmcp/tools/).
scrcpy-mcp AGENTS.md
Instructions for JuanCF/scrcpy-mcp, covering agents.md, project overview, project documentation, build/lint/test commands and build the project.
withings-mcp CLAUDE.md
Instructions for akutishevsky/withings-mcp, covering claude.md, general rules, project overview, development commands and running.
streamdeck-mcp CLAUDE.md
Instructions for verygoodplugins/streamdeck-mcp, covering claude.md, development commands, setup, run server (for claude desktop) and lint.
pixoo-mcp-server AGENTS.md
Instructions for cyanheads/pixoo-mcp-server, covering developer protocol, architecture overview, what's next?, core rules and patterns.
freecad-mcp copilot-instructions.md
Copilot instructions for sandraschi/freecad-mcp: You have access to 46+ FreeCAD CAD/CAM/CAE tools via MCP.