issue_requirements

issue_requirements is a skill for Claude Code from MarcusJellinghaus/mcp-tools-py. It costs 9 tokens per session (224 once invoked), scanned A, a copy of issue_requirements, MIT.

A review step that lists settled decisions, unresolved product questions, and constraints after an issue and codebase have been examined.

In plain words
What is it for?
Use it to prepare a focused requirements discussion before implementation.
Why use it?
It prevents settled decisions from being reopened and keeps the discussion focused on questions that affect user-facing behavior.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Good fit Use it to prepare a focused requirements discussion before implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marcusjellinghaus/mcp-tools-py/issue_requirements
Install

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.

Any agent
npx skills add MarcusJellinghaus/mcp-tools-py --skill issue_requirements
Clone the repo
git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-py

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.

agentmods badge for issue_requirements

README.md
[![agentmods](https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-py/issue_requirements/github.svg)](https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-py/issue_requirements)
Your own site
<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-py/issue_requirements"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-py/issue_requirements/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.

agentmods 80×15 button for issue_requirements

Your own site · 80×15
<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-py/issue_requirements"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-py/issue_requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 224 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.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00224
Opus 5 $0.00005 $0.00112
Sonnet 5 $0.00002 $0.00045
Haiku 4.5 $0.00001 $0.00022

Measured 8d ago against content hash 93332b04e8b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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

Origin

This is a copy

100% identical to issue_requirements — 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.

.claude/skills/issue_requirements/SKILL.md · 23 lines

What it actually says

Issue Requirements

Refocus the conversation on open requirements after /issue_analyse has explored the issue and codebase.

Instructions

Review the conversation so far and produce a structured summary:

  1. Decided items: List what was already decided (from the issue's ## Decisions section and the current conversation). Do not re-ask these.

  2. Questionable decisions: If any existing decision seems risky or worth revisiting given what you've seen in the code, briefly note why. Don't block on it — just flag it.

  3. Open requirements / feature questions: List only the remaining open questions that affect requirements or user-facing behavior. Implementation details are yours to decide — do not ask about them.

  4. Constraints & rationale identified: List any non-obvious constraints or gotchas discovered during analysis (the "why" behind decisions, things downstream steps need to know).

Suggested next step: /discuss — to walk through the open questions one by one.

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.

  1. 8d ago First seen · 23 lines · 9 tokens per session scan A 93332b04e8b5

Subscribe to this mod's changes

issue_requirements is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-py (18 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 224 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to issue_requirements, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

vibeue

Unreal Engine 5 development using the VibeUE Python API. Use when working in Unreal Engine — blueprints, state trees, materials, actors, landscapes, animation, niagara, widgets, sound, foliage, gameplay tags, enhanced input, skeletons, PCG (procedural content generation), and more. VibeUE is an extension of Unreal's…

kevinpbuckley/VibeUE · 82 tokens

test-generator

Generate pytest test cases for Python functions and classes.

vstorm-co/pydantic-deepagents · 12 tokens

python-design-pattern

Python design patterns and anti-patterns. Use when designing new components, refactoring, reviewing code for common mistakes, choosing abstractions, or evaluating pull requests for structural issues like tight coupling, leaking internal types, or error handling problems.

AI-Riksarkivet/ra-mcp · 51 tokens

testing-python

Write and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, async testing, and CI integration.

AI-Riksarkivet/ra-mcp · 48 tokens

exasol-udfs

Exasol User-Defined Functions (UDFs) and Scripts: CREATE SCRIPT syntax, language options, SQL-to-language data type mappings, ExaIterator API, BucketFS access, and Script Language Containers.

exasol/mcp-server · 48 tokens

scrape-batch

Extract many known URLs in one polite, rate-limited pass. Use when the user hands over a list of links, a set of search hits to read in full, or asks to "scrape these pages" / "pull the content from all of them". Drives extract(action="batch"), which fans out with per-domain rate limiting and returns partial results…

n24q02m/wet-mcp · 84 tokens