Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/marcusjellinghaus/mcp-workspace/implement_directnpx skills add MarcusJellinghaus/mcp-workspace --skill implement_directgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-workspaceWrote 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/marcusjellinghaus/mcp-workspace/implement_direct)<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="Measured on agentmods" 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 | $0.00002 | $0.00685 |
| Opus 5 | $0.00001 | $0.00342 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00068 |
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 4d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- implement-direct — 97% identical, 3 lines differ
- implement_direct — 86% identical, 7 lines differ
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.txtand extract the issue number from theIssue #NNNline - If the file doesn't exist or has no issue number, ask the user
Steps
-
Fetch issue details Call
mcp__mcp-workspace__github_issue_viewwith 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 issuesmcp__mcp-tools-py__run_pytest_check(withextra_args: ["-n", "auto"]) — fix all failuresmcp__mcp-tools-py__run_mypy_check— fix all issuesmcp__mcp-tools-py__run_ruff_check— fix all issues
-
Format code Use
mcp__mcp-tools-py__run_format_codeto 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
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.
- 4d ago First seen · 72 lines · 2 tokens per session scan A 4ff58f1ab3f9
implement-direct is a skill published in the GitHub repository MarcusJellinghaus/mcp-workspace (50 stars, last pushed 2d ago), licensed MIT. It adds 2 tokens to every session and 685 once invoked, about $0.0000 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-30.
Other skills, from other repositories
algorand-interaction
Interact with Algorand blockchain via the Algorand MCP server — wallet operations, ALGO/ASA transactions, smart contracts, account info, NFD lookups, atomic groups, Tinyman swaps, Haystack Router best-price swaps, Alpha Arcade prediction markets, Pera asset verification, TEAL compilation, knowledge base. Use when user…
alpha-arcade-interaction
Trade on Alpha Arcade prediction markets on Algorand — browse markets, read orderbooks, place limit/market orders, manage positions, cancel/amend orders, split/merge shares, and claim winnings. Use when user asks about prediction markets, event betting, YES/NO shares, orderbooks, or Alpha Arcade.
algorand-x402-payment
Execute x402 payments at runtime using Algorand MCP tools. Use whenever an HTTP request returns 402 Payment Required (or a PAYMENT-REQUIRED header), the user needs to access a paid API or x402-protected resource, or the user mentions x402, micropayments, paying for an endpoint, or "payment required" — even if they…
haystack-router-interaction
Route and execute optimal token swaps on Algorand using Haystack Router via Algorand MCP tools. Use when getting best-price quotes across multiple Algorand DEXes and LST protocols, executing atomic swaps, and checking asset opt-in — all through the Algorand MCP server.
chainstack
Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status, searching Chainstack docs, contacting the Chainstack team, or interacting with the Chainstack platform API via…
done
Use when the user signals work completion with 'done', 'fertig', 'finished', 'abschluss', '/done'. Detects current branch (main vs feature), runs closure checks defined in CLAUDE.md, handles commit and push based on branch context, closes related GitHub issues, and reports a strict short summary.