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/mdlopresti/mealie-mcp/github-issue-workflownpx skills add mdlopresti/mealie-mcp --skill github-issue-workflowgit clone --depth 1 https://github.com/mdlopresti/mealie-mcpWrote 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/mdlopresti/mealie-mcp/github-issue-workflow)<a href="https://agentmods.dev/skills/mdlopresti/mealie-mcp/github-issue-workflow"><img src="https://agentmods.dev/badge/skills/mdlopresti/mealie-mcp/github-issue-workflow.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.1 | $0.00027 | $0.01418 |
| Opus 5 | $0.00014 | $0.00709 |
| Sonnet 5 | $0.00005 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
github-issue-workflow scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Test endpoint manually with curl before implementing How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Workflow
Automates the complete development workflow for GitHub issues: select issue → feature branch → implement → test → PR → merge.
Usage
With specific issue:
/github-issue-workflow 21
Auto-select most impactful issue:
/github-issue-workflow
Workflow Steps
When this skill is invoked, execute the following workflow:
1. Select Issue
If issue number provided:
- Fetch issue details:
gh issue view <number> --json number,title,body,labels
If no issue number (auto-select):
- List open issues:
gh issue list --state open --json number,title,labels - Select most impactful based on:
- Priority: Labels with "high" priority first
- Type: "enhancement" over "bug" (unless critical bug)
- Dependencies: Issues blocking other work
- Effort: Quick wins (low effort, high impact) preferred
2. Create Feature Branch
Follow the git workflow pattern from CLAUDE.md:
# Determine branch prefix
# enhancement → feature/
# bug → fix/
git checkout main
git pull origin main
git checkout -b <prefix>/issue-<number>-<short-description>
Examples:
feature/issue-21-categories-crudfix/issue-6-bulk-operations
3. Implement Fix
Read the issue body for implementation tasks and requirements.
Standard implementation pattern:
- Check OpenAPI spec if implementing new endpoints
- Add client methods to
src/client.py - Add tool functions to appropriate
src/tools/*.pyfile - Add MCP tool wrappers in
src/server.py - Write comprehensive tests in
tests/test_tools_*.py - Update
CHANGELOG.mdwith changes
Follow existing patterns:
- Look at similar existing implementations
- Match error handling patterns
- Use consistent naming conventions
- Include docstrings with examples
4. Test Implementation
Run tests:
pytest tests/ -v
Type checking:
mypy src/
Fix any failures before proceeding.
5. Commit and Push
git add .
git commit -m "<type>: <description>
<details>
Fixes #<number>"
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.
- 5d ago First seen · 243 lines · 27 tokens per session scan A 21901ca6850a
github-issue-workflow is a skill published in the GitHub repository mdlopresti/mealie-mcp (6 stars, last pushed 8mo ago), licensed MIT. It adds 27 tokens to every session and 1,418 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
add-mechanic
Add game mechanics with correct GDScript 4.x patterns -- movement, health, inventory, save/load.
debug-issue
Systematic Godot debugging decision trees for physics, signals, rendering, navigation, and input issues.
build-scene
Pattern-based Godot scene construction with node hierarchy templates and companion node rules.
bulk-update
Update properties or content across many pages in a Notion database with dry-run and error recovery.
organize-database
Transform unstructured Notion pages into a well-designed database with proper schema and migration.
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.