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-status)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/gh-status"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-status/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-status"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-status.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.00397 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
gh-status 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 10d 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.
What it actually says
Workflow Status
Quick overview of current GitHub workflow state.
Process
-
Show assigned issues:
gh issue list --assignee @me --state open --json number,title,labels -
Show your open PRs:
gh pr list --author @me --state open --json number,title,reviewDecision,statusCheckRollup -
Show PRs awaiting your review:
gh pr list --search "review-requested:@me" --json number,title,author -
Show PRs with unaddressed feedback (your PRs with changes requested):
gh pr list --author @me --search "review:changes_requested" --json number,title
Output Format
## Workflow Status
### Your Assigned Issues (N)
- #12 Issue title [bug]
- #15 Another issue [enhancement]
### Your Open PRs (N)
- #20 PR title - Approved, checks passing
- #22 PR title - Changes requested
### Awaiting Your Review (N)
- #18 PR title by @author
### Needs Attention (N)
- #22 Has unaddressed review feedback
Status Indicators
| Status | Meaning |
|---|---|
| Approved | PR has been approved by reviewers |
| Changes requested | PR needs updates based on review feedback |
| Checks passing | All CI checks are green |
| Checks failing | One or more CI checks failed |
| Awaiting review | PR is waiting for review |
Usage
# Show workflow status
/gh-status
Rules
- This command is read-only (no modifications)
- Shows only items relevant to the current user
- Highlights items that need attention
- Groups information by category for quick scanning
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.
- 10d ago First seen · 70 lines · 0 tokens per session scan A bc1b99e06c47
gh-status is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 397 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.
ship
Ship workflow — detect base branch, merge, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
document-release
Post-ship documentation update — reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped.
deploy
Start Phase 6 — propose a deployment for human approval and, once approved, execute with post-deploy verification.
resolve-review
Resolve reviewer feedback - from GitHub PRs, chat, or any reviewer.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.