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 commands/vishnu2kmohan/mcp-server-langgraph/fix-issuegit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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/commands/vishnu2kmohan/mcp-server-langgraph/fix-issue)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/fix-issue"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/fix-issue.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.00011 | $0.00612 |
| Opus 5 | $0.00005 | $0.00306 |
| Sonnet 5 | $0.00002 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
fix-issue 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Issue Workflow
Automated workflow for debugging and fixing GitHub issues.
Usage: /fix-issue <issue-number> or /fix-issue $ARGUMENTS
Workflow Steps
-
Retrieve Issue Details
gh issue view $ARGUMENTS --json title,body,labels,commentsAnalyze:
- Issue title and description
- Labels (bug, enhancement, documentation, etc.)
- Existing comments and discussion
- Related PRs or issues
-
Reproduce the Issue
Based on issue type:
For Bugs:
- Identify affected component from description
- Write a minimal reproduction test case
- Run tests to confirm the bug
For Features:
- Review requirements and acceptance criteria
- Check for existing similar functionality
- Identify affected modules
For Documentation:
- Locate relevant documentation files
- Review current content vs. requested changes
-
Investigate Root Cause
- Search codebase for related code
- Read relevant files
- Check recent changes with git log/blame
- Review ADRs for architectural context
- Check CLAUDE.md for project conventions
-
Develop Solution
- Create fix/feature implementation
- Follow existing code patterns
- Maintain type hints and documentation
- Ensure backward compatibility
-
Test the Fix
make test-unit- Add new tests for the fix
- Ensure all existing tests still pass
- Run relevant integration tests if needed
- Check code coverage
-
Update Documentation
- Update CHANGELOG.md with details
- Update relevant documentation files
- Add/update docstrings
- Create/update ADR if architectural
-
Commit Changes
git add . git commit -m "fix: <description> (#$ARGUMENTS)"Follow conventional commit format:
- fix: for bug fixes
- feat: for new features
- docs: for documentation
- test: for tests
- refactor: for refactoring
-
Create Pull Request
gh pr create --fill
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 · 118 lines · 11 tokens per session scan A 105dd51b8d03
fix-issue is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 10d ago), licensed MIT. It adds 11 tokens to every session and 612 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 commands, from other repositories
hal-voice-toggle
Toggle HAL 9000 voice clips on or off.
deps-age
Analyze dependency freshness and maintenance activity.
designer
UI/UX design with Memory coordination for consistent experiences.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.
bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.
docker-logs
Muestra los logs recientes de un servicio Docker. El usuario puede especificar qué servicio.