Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dewtech-technologies/dare-methodnpx agentmods add skills/dewtech-technologies/dare-method/skill-mcp-serverWrote 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/skills/dewtech-technologies/dare-method/skill-mcp-server)<a href="https://agentmods.dev/skills/dewtech-technologies/dare-method/skill-mcp-server"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/skill-mcp-server/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/skills/dewtech-technologies/dare-method/skill-mcp-server"><img src="https://agentmods.dev/badge/skills/dewtech-technologies/dare-method/skill-mcp-server.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.00063 | $0.02862 |
| Opus 5.5 | $0.00025 | $0.01145 |
| Sonnet 5.5 | $0.00013 | $0.00572 |
| Haiku 4.5 | $0.00006 | $0.00286 |
Grade A, and why
skill-mcp-server 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 1mo 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 — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DARE MCP Server Skill
Você é um especialista em servidores MCP (Model Context Protocol da Anthropic). Seu papel é gerar servidores MCP bem estruturados, seguros, testáveis e publicáveis, expondo tools/resources/prompts via stdio, SSE ou HTTP.
Quando usar
- Você precisa expor capacidades para Claude Code, Cursor ou outro cliente MCP
- Você quer integrar uma API externa (Linear, GitHub, banco interno) como tool MCP
- Você está auditando um servidor MCP existente
O que é MCP em 30 segundos
MCP (Model Context Protocol) é um protocolo aberto da Anthropic para conectar agentes a fontes de dados e ações externas. Um servidor MCP expõe:
- Tools — funções chamáveis pelo agente (ex:
create_issue,query_db) - Resources — dados leitáveis (ex: documentos, schemas)
- Prompts — templates parametrizados
Transports suportados:
- stdio — agente spawnea processo local, comunica via stdin/stdout (mais simples)
- SSE — server remoto, agente conecta via Server-Sent Events
- HTTP — server remoto stateless
Stack canônica (TypeScript)
- Node 20+ com TypeScript 5.5+
- @modelcontextprotocol/sdk SDK oficial
- Zod para validação de input/output de tools
- vitest para testes
- eslint + prettier
Stack canônica (Python)
- Python 3.11+
- mcp SDK oficial (
pip install mcp) - Pydantic v2 para schemas
- pytest + pytest-asyncio
- ruff + mypy
Estrutura recomendada (TypeScript)
mcp-meu-server/
├── package.json
├── tsconfig.json
├── src/
│ ├── index.ts ← entrypoint (stdio)
│ ├── server.ts ← criação do MCP Server
│ ├── tools/
│ │ ├── create_issue.ts
│ │ └── search_issues.ts
│ ├── resources/
│ │ └── schema.ts
│ ├── prompts/
│ │ └── issue_template.ts
│ ├── schemas/ ← Zod schemas
│ └── lib/
│ └── linear-client.ts ← cliente da API externa
└── tests/
Exemplo: server stdio TypeScript
// src/index.ts
import { Server } from '@modelcontextprotocol/sdk/server/index.js';
import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
import { registerTools } from './tools/index.js';
import { registerResources } from './resources/index.js';
const server = new Server(
{ name: 'meu-mcp-server', version: '1.0.0' },
{ capabilities: { tools: {}, resources: {}, prompts: {} } }
);
registerTools(server);
registerResources(server);
const transport = new StdioServerTransport();
await server.connect(transport);
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.
- 1mo ago First seen · 383 lines · 63 tokens per session scan A 83611dd4cdaf
skill-mcp-server is a skill published in the GitHub repository dewtech-technologies/dare-method (5 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 2,862 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
writing-skills
Use when creating a new skill for the Shipworthy plugin, or when a recurring failure mode needs to be codified into a reusable guide. Covers TDD-for-documentation, CSO (Claude Search Optimization), adversarial testing, and the full skill lifecycle.
production-readiness
Pre-launch checklist covering security, performance, reliability, legal, SEO, monitoring, backups, and custom domains. Each item has both a plain-language explanation and technical implementation detail. Ensures nothing critical is missed before going live.
design-documents
Formal RFC/design doc template for significant engineering changes. Covers context, goals, non-goals, proposed solution, alternatives considered, data model changes, API changes with backward compatibility analysis, security considerations, performance implications, rollout plan, rollback plan, second-order effects…
compliance-awareness
Practical engineering guidance for SOC 2, GDPR, HIPAA compliance and data classification. Covers access controls, audit logging, change management, right to deletion, data portability, consent, PHI encryption, and data classification levels. Engineering checks, not legal advice.
threat-modeling
Apply the STRIDE framework to identify and mitigate security threats. Covers Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege with practical questions, verification steps, and mitigations for each threat category.
distributed-systems
Apply distributed systems patterns including idempotency, saga pattern, outbox pattern, eventual consistency, and CQRS to build reliable, consistent distributed services.