Borrowing it
Nothing to install: this file belongs to syamaner/coffee-roaster-mcp. 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/syamaner/coffee-roaster-mcp/main/.claude/skills/release-registry/SKILL.mdgit clone --depth 1 https://github.com/syamaner/coffee-roaster-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/skills/syamaner/coffee-roaster-mcp/release-registry)<a href="https://agentmods.dev/skills/syamaner/coffee-roaster-mcp/release-registry"><img src="https://agentmods.dev/badge/skills/syamaner/coffee-roaster-mcp/release-registry/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/syamaner/coffee-roaster-mcp/release-registry"><img src="https://agentmods.dev/badge/skills/syamaner/coffee-roaster-mcp/release-registry.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.00022 | $0.00607 |
| Opus 5 | $0.00011 | $0.00303 |
| Sonnet 5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
release-registry 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Registry - RoastPilot
Use this skill only for read-only package and registry release preparation or audit. Agents do not tag, approve environments, publish, or perform live verification.
Current Scope
v0.1.16is published on PyPI and in the MCP Registry.docs/release.mdis the current release authority and preserves historical outcomes.- Tags, release-environment approval, publication, and live verification are
human-operator-only. The intended future
0.2.0line is not authority to tag or publish.
Release Targets
- Package name:
coffee-roaster-mcp - MCP Registry name:
io.github.syamaner/coffee-roaster-mcp - Display title:
RoastPilot
Human-Owned Release Flow
- Confirm the package version is intentional.
- Build and validate sdist plus wheel artifacts.
- Confirm README contains the MCP verification string when the release story adds it.
- Confirm
server.jsonexists and matches the package version when the registry metadata story lands. - The human operator publishes the package to PyPI.
- The human operator verifies it in a clean environment.
- The human operator runs published-package mock-safe smoke checks.
- The human operator publishes MCP Registry metadata.
- The human operator verifies the registry listing.
Current Review Checklist
Use this skill to review readiness only:
- package name is still
coffee-roaster-mcp - registry name is still
io.github.syamaner/coffee-roaster-mcp - release docs do not imply hardware-ready support without Hottop validation
- default first-crack mode remains
disabledso package install smoke does not require audio or model download - version alignment across package metadata, tags, and
server.jsonremains part of the release plan
Mock-Safe Published Smoke Target
For a human-owned published-package verification, the minimum smoke target is:
coffee-roaster-mcp --help
coffee-roaster-mcp --version
python -c "import os, tempfile; from coffee_roaster_mcp.config import load_config; tmp = tempfile.TemporaryDirectory(); os.chdir(tmp.name); c = load_config(environ={}); print(c.roaster.driver, c.first_crack.mode, c.first_crack.precision); tmp.cleanup()"
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 Changed · +6 lines · -12 tokens per session 51c09aa45a22
- 11d ago First seen · 65 lines · 34 tokens per session scan A a7ac97a81f9b
release-registry is a skill published in the GitHub repository syamaner/coffee-roaster-mcp (0 stars, last pushed 7d ago), licensed Apache-2.0. It adds 22 tokens to every session and 607 once invoked, about $0.0001 per session on Opus 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
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.
metagit-cli
CLI-only shortcuts for metagit agents — workspace catalog, discovery, prompts, sync, layout, and config. Use instead of MCP or HTTP API when operating from a shell or agentmode session.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
cortex-profile
View and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile'…
perseus
Use when you need a bounded, local Perseus context render before an assistant reads project state. Perseus resolves selected workspace inputs such as git, services, sessions, and task notes into markdown. Use for deterministic session starts, workspace audits, and explicit context handoffs.