Borrowing it
Nothing to install: this file belongs to docdyhr/simplenote-mcp-server. 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/docdyhr/simplenote-mcp-server/main/.claude/skills/mcp-release-qa/SKILL.mdgit clone --depth 1 https://github.com/docdyhr/simplenote-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/docdyhr/simplenote-mcp-server/mcp-release-qa)<a href="https://agentmods.dev/skills/docdyhr/simplenote-mcp-server/mcp-release-qa"><img src="https://agentmods.dev/badge/skills/docdyhr/simplenote-mcp-server/mcp-release-qa/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/docdyhr/simplenote-mcp-server/mcp-release-qa"><img src="https://agentmods.dev/badge/skills/docdyhr/simplenote-mcp-server/mcp-release-qa.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.00058 | $0.01465 |
| Opus 5.5 | $0.00023 | $0.00586 |
| Sonnet 5.5 | $0.00012 | $0.00293 |
| Haiku 4.5 | $0.00006 | $0.00146 |
Grade A, and why
mcp-release-qa 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 yesterday.
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-release-qa — 0 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Release QA
Test the server that users will run. A schema review or a passing unit test is not runtime evidence.
This skill complements security review. It focuses on protocol behavior, published-contract drift, transport correctness, and reproducible release evidence.
Rules
- Run checks against a fresh server process built from the candidate revision.
- Keep
initialize,notifications/initialized, discovery, and invocation in the same session. A new process is a new STDIO session. - Treat source registrations as implementation truth and public documentation as a contract that must match it.
- Record exact commands and raw responses. Do not replace missing evidence with "looks correct."
- Do not invoke mutation-capable tools against production data. Use fixtures, a sandbox, or stop and name the missing safe test environment.
- Derive the expected capability inventory from the candidate source on every run.
1. Establish the release surface
Identify:
- candidate commit and build command;
- server entry point and transport: STDIO, Streamable HTTP, or SSE;
- supported MCP protocol versions;
- source files that register tools, resources, resource templates, and prompts;
- generated catalogs, manifests, README tables, and install instructions;
- existing protocol, integration, and smoke-test commands.
Prefer repository-native commands. Inspect package.json, pyproject.toml,
Makefile, CI workflows, and contributor instructions before inventing a test
harness.
2. Start a clean server
Build the candidate and start the documented entry point with test-safe configuration. Capture:
- the exact command;
- commit SHA;
- environment variable names, with values redacted;
- stdout, stderr, and exit status;
- the endpoint or child-process transport used by the client.
For STDIO, stdout is protocol-only. Logs, banners, and stack traces belong on stderr. For HTTP transports, record the status, relevant MCP headers, and session identifier handling without printing credentials.
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.
- yesterday First seen · 199 lines · 58 tokens per session scan A 36b5a18d8dde
mcp-release-qa is a skill published in the GitHub repository docdyhr/simplenote-mcp-server (21 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 1,465 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to mcp-release-qa, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
enterprise-integration-testing
Use when testing enterprise integrations across SAP, middleware, WMS, or backend systems, validating E2E enterprise flows, testing SAP-specific patterns (RFC, BAPI, IDoc, OData, Fiori), or enforcing cross-system quality gates.
api-testing-patterns
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.
springboot-tdd
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
Integration Testing Patterns
Integration testing strategies including database integration, external service integration, message queue testing, and test container patterns.
contract-test-engineer
Use when the user asks to verify compatibility between an API provider and consumer, SDK and service, event producer and consumer, schema versions, or serialized data. Define and test the shared contract, including failures and compatibility rules, before changing either side.
salvo-testing
Write unit and integration tests for Salvo applications using TestClient. Use for testing handlers, middleware, and API endpoints.