Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
Rules for measuring or quoting any benchmark number in this repo.
$ npx skills add jgravelle/jcodemunch-mcp --skill benchmark-methodology -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jgravelle/jcodemunch-mcp benchmark-methodology --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jgravelle/jcodemunch-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/benchmark-methodology .claude/skills/benchmark-methodology && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "benchmark-methodology" agent skill from https://github.com/jgravelle/jcodemunch-mcp/tree/main/.claude/skills/benchmark-methodology into .claude/skills/benchmark-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-methodology", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jgravelle/jcodemunch-mcp/tree/main/.claude/skills/benchmark-methodologyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jgravelle/jcodemunch-mcp --skill benchmark-methodology -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jgravelle/jcodemunch-mcp benchmark-methodology --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jgravelle/jcodemunch-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/benchmark-methodology .agents/skills/benchmark-methodology && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "benchmark-methodology" agent skill from https://github.com/jgravelle/jcodemunch-mcp/tree/main/.claude/skills/benchmark-methodology into .agents/skills/benchmark-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-methodology", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jgravelle/jcodemunch-mcp --skill benchmark-methodology -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jgravelle/jcodemunch-mcp benchmark-methodology --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jgravelle/jcodemunch-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/benchmark-methodology .cursor/skills/benchmark-methodology && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "benchmark-methodology" agent skill from https://github.com/jgravelle/jcodemunch-mcp/tree/main/.claude/skills/benchmark-methodology into .cursor/skills/benchmark-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-methodology", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jgravelle/jcodemunch-mcp.git --path .claude/skills/benchmark-methodology--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jgravelle/jcodemunch-mcp --skill benchmark-methodology -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jgravelle/jcodemunch-mcp benchmark-methodology --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jgravelle/jcodemunch-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/benchmark-methodology .gemini/skills/benchmark-methodology && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "benchmark-methodology" agent skill from https://github.com/jgravelle/jcodemunch-mcp/tree/main/.claude/skills/benchmark-methodology into .gemini/skills/benchmark-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-methodology", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jgravelle/jcodemunch-mcp benchmark-methodologyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jgravelle/jcodemunch-mcp --skill benchmark-methodology -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jgravelle/jcodemunch-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/benchmark-methodology .github/skills/benchmark-methodology && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "benchmark-methodology" agent skill from https://github.com/jgravelle/jcodemunch-mcp/tree/main/.claude/skills/benchmark-methodology into .github/skills/benchmark-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-methodology", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jgravelle/jcodemunch-mcp --skill benchmark-methodology -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jgravelle/jcodemunch-mcp benchmark-methodology --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jgravelle/jcodemunch-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/benchmark-methodology .opencode/skills/benchmark-methodology && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "benchmark-methodology" agent skill from https://github.com/jgravelle/jcodemunch-mcp/tree/main/.claude/skills/benchmark-methodology into .opencode/skills/benchmark-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "benchmark-methodology", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
benchmark-methodologyRules for measuring or quoting any benchmark number in this repo.
Benchmark Methodology is an agent skill from jgravelle/jcodemunch-mcp. Rules for measuring or quoting any benchmark number in this repo. Load before running the bench tier, writing a delta into a PR or CHANGELOG, or touching anything under benchmarks/.
Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Changelog and release notes and MCP servers. It works with Model Context Protocol. The repository describes itself as: Cut AI token costs 95%+ on code exploration. The leading MCP server for precise, symbol-level GitHub code retrieval via tree-sitter AST. Works with Claude Code, Cursor & any MCP…
8 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 526da05. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
uvFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Benchmark Methodology loads about 438 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 191 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 191 words (~438 tokens).
“Authority: docs/harness/ARCHAEOLOGY.md (the benchmark rows), benchmarks/METHODOLOGY.md, benchmarks/REPRODUCING.md, CLAUDE.md Practice 4, docs/harness/FINDINGS.md F-10, F-13, F-17.”
Just SKILL.md in .claude/skills/benchmark-methodology of jgravelle/jcodemunch-mcp.
Open the folder on GitHubat commit 526da05
Benchmark Methodology next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Benchmark Methodology this skilljgravelle/jcodemunch-mcp | 2.7k | — | ~438 | Automated safety check: Pass | Custom licence | |
| Project Releaseswimmwatch/cloakbrowser-mcp | 164 | — | ~1.9k | Automated safety check: Pass | MIT | |
| ReleasePrefectHQ/fastmcp | 28k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Reading Livekit Docslivekit-examples/agent-starter-python | 264 | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| MCP Server Trello Releasedelorenj/mcp-server-trello | 445 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Githits Releasegithits-com/githits-cli | 115 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 |
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
livekit-examples/agent-starter-python
Looks up current LiveKit facts (API signatures, CLI flags, config options, model and provider support, SDK changelogs, pricing) from the docs instead of answering from memory.
delorenj/mcp-server-trello
Canonical build → release → tag → publish procedure for the @delorenj/mcp-server-trello repo.
githits-com/githits-cli
A skill your agent uses when maintaining the GitHits changelog or preparing, reviewing, or executing a GitHits release.
JasonColapietro/suede-creator-skills
Suede-owned launch packaging and install verification. An agent skill from JasonColapietro/suede-creator-skills.
jgravelle/jcodemunch-mcp
Publishing a jMunch release (jcodemunch-mcp, jdocmunch-mcp, jdatamunch-mcp, jragmunch-cli), reviewing/merging/closing PRs, and responding to the community.
jgravelle/jcodemunch-mcp
Context for the jcodemunch-observatory weekly scorecard — what it tracks, the Monday 06:00 UTC cron, why scores must be pulled live rather than transcribed, the NestJS grade story, and the…
jgravelle/jcodemunch-mcp
The PR title and body template, and the rules for any comment drafted for a reporter or contributor.
jgravelle/jcodemunch-mcp
The shape of a CHANGELOG.md entry and heading in this repo. An agent skill from jgravelle/jcodemunch-mcp.
jgravelle/jcodemunch-mcp
How to keep CLAUDE.md under its character Floor without deleting a rule: measure sections first, rotate by derivability, two edits per rotation.
jgravelle/jcodemunch-mcp
The two questions that separate a fix for the reported spelling from a fix for the property.
Works with
Rules for measuring or quoting any benchmark number in this repo. Benchmark Methodology is an agent skill from jgravelle/jcodemunch-mcp. Rules for measuring or quoting any benchmark number in this repo.
Benchmark Methodology fits situations like: tasks that involve Changelog and release notes; tasks that involve MCP servers.
Run `npx skills add jgravelle/jcodemunch-mcp --skill benchmark-methodology -a claude-code`. Or copy the skill folder (.claude/skills/benchmark-methodology in jgravelle/jcodemunch-mcp) into .claude/skills/benchmark-methodology in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jgravelle/jcodemunch-mcp --skill benchmark-methodology -a codex`. Or copy the skill folder (.claude/skills/benchmark-methodology in jgravelle/jcodemunch-mcp) into .agents/skills/benchmark-methodology in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jgravelle/jcodemunch-mcp --skill benchmark-methodology -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/benchmark-methodology, .gemini/skills/benchmark-methodology, .github/skills/benchmark-methodology and .opencode/skills/benchmark-methodology in your project.
Going by SKILL.md and its folder, Benchmark Methodology needs the command-line tools its instructions call (uv). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Benchmark Methodology has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 438 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Benchmark Methodology: Project Release (swimmwatch/cloakbrowser-mcp, 164 stars), Release (PrefectHQ/fastmcp, 28k stars), Reading Livekit Docs (livekit-examples/agent-starter-python, 264 stars) and MCP Server Trello Release (delorenj/mcp-server-trello, 445 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jgravelle (a GitHub user) maintains it in jgravelle/jcodemunch-mcp, which has 2,749 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 2026.
Source: jgravelle/jcodemunch-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.