What is implement-direct?

A workflow for implementing a small, clearly defined GitHub issue directly. GitHub issues are written tasks or bug reports, often with acceptance criteria describing when the work is complete.

Use it to fetch an issue, create or switch to its code branch, inspect relevant files, and make the smallest required implementation.

It removes the overhead of creating a plan or tracking a separate task when the requested change is already well understood. It also checks related issues and the existing code before editing.

How MarcusJellinghaus/mcp-workspace configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to MarcusJellinghaus/mcp-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/MarcusJellinghaus/mcp-workspace/main/.claude/skills/implement_direct/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-workspace

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/implement_direct/github.svg)](https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/implement_direct)

Your own site

<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/implement_direct"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/implement_direct/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/implement_direct"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/implement_direct.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 685 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00002	$0.00685
Opus 5.5	$0.00001	$0.00274
Sonnet 5.5	$0.00000	$0.00137
Haiku 4.5	$0.00000	$0.00068

Measured 1mo ago against content hash 4ff58f1ab3f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement-direct 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

implement-direct — 97% identical, 5 lines differ
implement_direct — 86% identical, 7 lines differ

.claude/skills/implement_direct/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement Direct

Implement a small, well-defined issue directly — no planning phase, no task tracker.

Resolve Issue Number

The user may provide an issue number as the argument (available as $ARGUMENTS). If no issue number is provided:

Read .vscodeclaude_status.txt and extract the issue number from the Issue #NNN line
If the file doesn't exist or has no issue number, ask the user

Steps

Fetch issue details Call mcp__mcp-workspace__github_issue_view with the issue number. Read the issue title, description, and acceptance criteria carefully. Read linked issues first. If the issue points to an epic, design doc, dependencies, or sibling issues, read those before implementing — it may not be self-contained, and any "read first" note is mandatory.

Checkout/create issue branch

mcp-coder gh-tool checkout-issue-branch <issue_number>

Understand context
- Read relevant source files referenced in the issue
- Understand the existing code patterns and conventions
- Identify the minimal set of changes needed
Implement changes
- Make the required code changes directly
- Follow existing code patterns and conventions
- Keep changes focused and minimal — only what the issue requires
Run quality checks
- mcp__mcp-tools-py__run_pylint_check — fix all issues
- mcp__mcp-tools-py__run_pytest_check (with extra_args: ["-n", "auto"]) — fix all failures
- mcp__mcp-tools-py__run_mypy_check — fix all issues
- mcp__mcp-tools-py__run_ruff_check — fix all issues
Format code Use mcp__mcp-tools-py__run_format_code to format all code (black + isort).

Update issue status

mcp-coder gh-tool set-status status-07:code-review

Suggest follow-up steps
- /commit_push — commit and push changes
- /check_branch_status — verify branch is clean
- /implementation_review — request a review of the implementation

Scope Guidance

Read the full file on GitHub · 72 lines

Changes

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 · 72 lines · 2 tokens per session scan A 4ff58f1ab3f9

Subscribe to this mod's changes

implement-direct is a skill published in the GitHub repository MarcusJellinghaus/mcp-workspace (48 stars, last pushed today), licensed MIT. It adds 2 tokens to every session and 685 once invoked, about $0.0000 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-30.

Project management claude-desktop file-operations filesystem mcp mcp-server model-context-protocol

report-issue

File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.

cyanheads/git-mcp-server · 51 tokens

build-flow

Create or change a Keboola flow that runs extractors, transformations and writers in order, optionally on a schedule. Use when the user wants to orchestrate, chain or schedule existing Keboola configurations.

keboola/mcp-server · 43 tokens

reviewing-sla-definitions

Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…

jschuller/mcp-server-servicenow · 79 tokens

mcp-workspace: Skill for Claude Code