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.
git clone --depth 1 https://github.com/opsmill/infrahub-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/commands/opsmill/infrahub-mcp/create-issue)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/create-issue"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/create-issue/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.
<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/create-issue"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/create-issue.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.01288 |
| Opus 5.5 | $0.00007 | $0.00515 |
| Sonnet 5.5 | $0.00004 | $0.00258 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
create-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 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.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Issue
Introduction
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues that follow project conventions and best practices. This command provides flexible detail levels to match your needs.
Prerequisites
- GitHub CLI (
gh) installed and authenticated - Current directory is within the infrahub-mcp repository
Feature Description
#$ARGUMENTS
Main Tasks
1. Repository Research & Context Gathering
- Identify the repository and confirm access:
gh repo view --json nameWithOwner -q '.nameWithOwner' - Check for related existing issues:
gh issue list --state open --limit 20 gh issue search "<keywords>" --limit 10 - Review project structure for relevant context:
dev/constitution.md— project principlesdev/knowledge/architecture.md— architecture overviewsrc/infrahub_mcp/— source code layout
- Identify relevant labels:
gh label list - Check recent PRs for similar patterns:
gh pr list --state merged --limit 10
2. Issue Planning & Structure
Title & Categorization:
- Draft clear, searchable issue title using conventional format (e.g.,
feat:,fix:,docs:) - Identify appropriate labels from repository's label set
- Determine issue type: enhancement, bug, documentation, refactor
- Consider adding priority labels if available
Stakeholder Analysis:
- Identify who will be affected by this issue (MCP users, developers, operators)
- Note any cross-project dependencies (infrahub-sdk, FastMCP)
Content Planning:
- Choose appropriate detail level based on issue complexity and audience
- List all necessary sections for the chosen template
- Gather supporting materials (error logs, configuration examples)
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 · 199 lines · 18 tokens per session scan A fd46566e8455
create-issue is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 1,288 once invoked, about $0.0001 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-31.
Other commands, from other repositories
hep-graph.body
A command for viewing saved Agentlas automation graphs and requesting that one be run. The desktop app performs the actual run.
fire-execute-plan
Execute a single plan with segment-based routing, per-task atomic commits, and test enforcement.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.