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/openshift-eng/ai-helpers/reconcile-githubgit clone --depth 1 https://github.com/openshift-eng/ai-helpersWrote 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/openshift-eng/ai-helpers/reconcile-github)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/reconcile-github"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/reconcile-github.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.02181 |
| Opus 5 | $0.00005 | $0.01091 |
| Sonnet 5 | $0.00002 | $0.00436 |
| Haiku 4.5 | $0.00001 | $0.00218 |
Grade A, and why
reconcile-github 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 2d 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
1 near-identical copy found in the catalogue:
- reconcile-github — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:reconcile-github
Synopsis
/jira:reconcile-github [options]
Description
The jira:reconcile-github command identifies and reports state mismatches between linked GitHub and Jira issues according to a configurable state mapping. This command is useful for:
- Ensuring Jira issues stay synchronized with their linked GitHub issues
- Identifying issues that need status updates
- Maintaining workflow consistency between GitHub and Jira
- Auditing cross-platform issue tracking accuracy
The command uses the gh2jira utility to perform the reconciliation. Use /jira:setup-gh2jira to install and configure gh2jira if you haven't already.
Implementation
📋 Phase 1: Validate Prerequisites
Check that the gh2jira utility is available and configured:
-
Verify gh2jira binary exists:
which gh2jira || echo "gh2jira not found. Run /jira:setup-gh2jira to install." -
Verify configuration files exist:
- Check for
tokenstore.yamlin the gh2jira directory - Check for
profiles.yamlif using profiles - Check for
workflows.yamlfor state mapping configuration - If missing, provide instructions on creating them
- Check for
-
Check for required tokens:
- GitHub token (in tokenstore.yaml)
- Jira token (in tokenstore.yaml)
If prerequisites are missing:
- Inform user about missing requirements
- Provide setup instructions (see Error Handling section)
🔍 Phase 2: Parse Arguments
Parse command arguments:
Optional flags:
--github-project <org/repo>: GitHub project (e.g.,operator-framework/operator-lifecycle-manager)--jira-project <key>: Jira project to reconcile (e.g.,OCPBUGS,CNTRLPLANE)--profile <name>: Use named profile from profiles.yaml--porcelain: Output in machine-readable format for scripting--output <format>: Output format for porcelain mode (jsonoryaml, default:json)
Argument validation:
- If
--profileis not used, both--github-projectand--jira-projectshould be provided - If
--porcelainis used,--outputspecifies the format
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.
- 2d ago First seen · 297 lines · 11 tokens per session scan A 588a025aeb23
reconcile-github is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 2,181 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-09-03.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.