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/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/gh-issue)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/gh-issue"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-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/synaptiai/synapti-marketplace/gh-issue"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-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.00000 | $0.01928 |
| Opus 5.5 | $0.00000 | $0.00771 |
| Sonnet 5.5 | $0.00000 | $0.00386 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
gh-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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Issue
Create a new GitHub issue following solution-agnostic principles.
Tool Usage: This workflow uses the AskUserQuestion tool extensively for interactive dialogues. Use it to clarify ambiguity, offer choices with tradeoffs, and gather missing context.
Phase 1: Gather Requirements
-
Use the AskUserQuestion tool to gather missing information:
- Context: What's the background? Why is this needed?
- Current State: What's the problem? (describe behavior, not implementation)
- Objective: What should be achieved? (outcomes, not methods)
- Acceptance Criteria: How do we know it's complete? (observable behavior)
-
Extract keywords from the user's description for duplicate detection
-
Check for milestones:
gh api repos/{owner}/{repo}/milestones --jq '.[] | "\(.number): \(.title)"'If milestones exist, use AskUserQuestion tool:
- Option 1: "No milestone"
- Option 2: "[Milestone name]" (for each active milestone)
Phase 2: Search for Existing Issues
Before creating a new issue, check for potential duplicates:
-
Search open issues using relevant keywords:
gh issue list --state open --search "RELEVANT_KEYWORDS" -
Search closed issues (may have already been solved):
gh issue list --state closed --search "RELEVANT_KEYWORDS" -
If matches found, use the AskUserQuestion tool:
Present the findings and offer choices:
- Option 1: Proceed - "Create new issue (these are different enough)"
- Option 2: View existing - "View issue #{number} instead"
- Option 3: Cancel - "This is a duplicate, don't create"
Include in the question: issue numbers, titles, and states of potential duplicates.
-
If related issues found but not duplicates, use AskUserQuestion tool:
- Option 1: "Create new issue, link as 'Related to #X'"
- Option 2: "Create new issue without linking"
- Option 3: "View related issue first"
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 · 260 lines · 0 tokens per session scan A 7608b4d3142b
gh-issue is a command published in the GitHub repository synaptiai/synapti-marketplace (7 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,928 tokens. 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
create-worktree
Follow these steps to create a git worktree.
omni-plan
ProductionOS flagship — 13-step orchestrative pipeline with tri-tiered evaluation, recursive convergence, CEO/Eng/Design review chain, CLEAR framework evaluation, multi-model judge tribunal, and autonomous PIVOT/REFINE/PROCEED decisions. Targets 100% production-ready output.
start
Activate the SDLC workflow (opt-in), re-enable after suspension, or start a new task when already enabled. On fresh install — auto-detects repo/CI/stack/tracker (≤3 prompts), creates .enabled, takes a one-sentence task description, and auto-generates scope.md and a draft plan. On re-enable — verifies the suspension…
build
Start Phase 4 — implement the approved design with surgical-edit discipline and work-item traceability.
status
Show the current in-flight task state — active phase, plan, gate, sign-off progress, and next action. Read-only; writes nothing.
create-task
Create one bounded task contract from a short request or optional structured brief, while routing unambiguous feedback on an existing task back to its defect cycle instead of duplicating work.