Borrowing it
Nothing to install: this file belongs to t1nk333r/mcp-dockhand. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/t1nk333r/mcp-dockhand/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/t1nk333r/mcp-dockhandWrote 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/t1nk333r/mcp-dockhand/copilot-instructions)<a href="https://agentmods.dev/instructions/t1nk333r/mcp-dockhand/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/t1nk333r/mcp-dockhand/copilot-instructions/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.
<a href="https://agentmods.dev/instructions/t1nk333r/mcp-dockhand/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/t1nk333r/mcp-dockhand/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.00758 | $0.00758 |
| Opus 5 | $0.00379 | $0.00379 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
mcp-dockhand 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 8d 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.
This is a copy
100% identical to mcp-dockhand copilot-instructions.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — MCP-Dockhand
Project Context
This is a Model Context Protocol (MCP) server for Dockhand Docker Management. It wraps the Dockhand REST API into 130+ MCP tools using Streamable HTTP transport.
Upstream repositories (source of truth for API behavior):
- Dockhand Server: https://github.com/finsys/dockhand (SvelteKit, Bun)
- Hawser Agent: https://github.com/finsys/hawser (Go)
Critical: Verify Against Upstream
When reviewing MCP tool implementations, always cross-reference with the upstream Dockhand source code:
- HTTP Methods: Check
src/routes/api/**/+server.tsin finsys/dockhand for the correct HTTP method (GET/POST/PUT/DELETE/PATCH). Our MCP tools MUST match. - Request Body Fields: Check the actual request parsing in the Dockhand route handlers to verify parameter names and types match what our tools send.
- Response Format: Verify our tools correctly handle the response structure (JSON object vs array, pagination, error format).
- Hawser Protocol: For environment/hawser-related tools, check
internal/protocol/messages.goandinternal/docker/compose.goin finsys/hawser. - API Schema: Compare against
docs/dockhand-api-schema.json(auto-generated daily from upstream source).
If a tool's implementation differs from upstream, flag it as HIGH priority.
Code Review Guidelines
Security
- All path parameters MUST use
encodePath()fromsrc/utils/encode-path.ts - No hardcoded credentials or tokens
- Session cookies must not be logged
- Environment filter must be applied on all environment-scoped endpoints
additionalConfig/additionalSettingsmust be merged BEFORE explicit fields (not after)
MCP Tool Quality
- All parameters must have Zod validation with
.describe()annotations - Tool descriptions must be clear and actionable for LLMs
- Prefer explicit typed parameters over generic
Record<string, unknown> - Required vs optional parameters must match the Dockhand API
connectionTypegating: host/port only forhawser-standard, nothawser-edge
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.
- 8d ago First seen · 65 lines · 758 tokens per session scan A 7ffcc0975cd3
mcp-dockhand copilot-instructions.md is an instructions file published in the GitHub repository t1nk333r/mcp-dockhand (0 stars, last pushed 16d ago), licensed MIT. It adds 758 tokens to every session, about $0.0038 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mcp-dockhand copilot-instructions.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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).
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).
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.
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.