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/huuthangntk/dokploy-mcp/agents-mdgit clone --depth 1 https://github.com/huuthangntk/dokploy-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/huuthangntk/dokploy-mcp/agents-md)<a href="https://agentmods.dev/instructions/huuthangntk/dokploy-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/huuthangntk/dokploy-mcp/agents-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.03862 | $0.03862 |
| Opus 5 | $0.01931 | $0.01931 |
| Sonnet 5 | $0.00772 | $0.00772 |
| Haiku 4.5 | $0.00386 | $0.00386 |
Grade A, and why
dokploy-mcp AGENTS.md scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "http://127.0.0.1:3000/mcp?debug=true" \ How it starts
The opening of the file, as written. The whole thing — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Welcome to the Smithery TypeScript MCP Server Scaffold!
This is the template project that gets cloned when you run npx create-smithery. It provides everything you need to build, test, and deploy a Model Context Protocol (MCP) server with Smithery.
What's Included
- TypeScript MCP Server with Zod-based configuration schema support
- Example Tool (
hellotool with debug mode configuration) - Example Resource (
history://hello-worldwith Hello World origin story) - Example Prompt (
greetprompt for generating greeting messages) - Development Workflow (
npm run devfor local testing with hot reload) - Deployment Ready configuration for the Smithery platform
- Session Management via
createStatefulServerorcreateStatelessServerwith optional config schemas
Quick Start Commands
# Run development server (streamable HTTP on port 3000)
npm run dev
# Build for production
npm run build
Development Workflow
Based on the Model Context Protocol architecture, MCP servers provide three core primitives:
1. Tools (for actions)
Add executable functions that AI applications can invoke to perform actions:
// Add a tool
server.registerTool(
"hello",
{
title: "Hello Tool",
description: "Say hello to someone",
inputSchema: { name: z.string().describe("Name to greet") },
},
async ({ name }) => {
// Access session config if using stateful server
const greeting = config.debug
? `DEBUG: Hello, ${name}!`
: `Hello, ${name}!`
return {
content: [{ type: "text", text: greeting }],
}
},
)
2. Resources (for static data)
Add data sources that provide contextual information:
// Add a resource
server.registerResource(
"hello-world-history",
"history://hello-world",
{
title: "Hello World History",
description: "The origin story of the famous 'Hello, World' program",
},
async uri => ({
contents: [
{
uri: uri.href,
text: '"Hello, World" first appeared in a 1972 Bell Labs memo by Brian Kernighan and later became the iconic first program for beginners in countless languages.',
mimeType: "text/plain",
},
],
}),
)
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 · 533 lines · 3,862 tokens per session scan A c254fcf2a336
dokploy-mcp AGENTS.md is an instructions file published in the GitHub repository huuthangntk/dokploy-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 3,862 tokens to every session, about $0.0193 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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).