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-plugin)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/gh-plugin"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-plugin.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.00000 | $0.01420 |
| Opus 5 | $0.00000 | $0.00710 |
| Sonnet 5 | $0.00000 | $0.00284 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
gh-plugin 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 7d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Plugin: $ARGUMENTS
Validate plugin structure and configuration before committing changes.
Tool Usage: This workflow uses the AskUserQuestion tool to clarify which plugins to validate and determine how to handle validation issues.
Arguments
$ARGUMENTS: Plugin name (optional)- If provided, validates the specified plugin
- If omitted, validates all plugins in the marketplace
Process
-
Identify plugins to validate:
# List all plugins ls -d plugins/*/If multiple plugins exist and no argument provided, use the AskUserQuestion tool:
- Option 1: "Validate all plugins"
- Option 2: "Validate specific plugin: [name]" (for each plugin)
-
For each plugin, run validation checks (see checklist below)
-
Report results with clear pass/fail status for each check
-
If issues found, use the AskUserQuestion tool to determine action:
- Option 1: "Fix these issues automatically" (if auto-fixable)
- Option 2: "Show me how to fix manually"
- Option 3: "Ignore and continue" (for non-critical issues)
- Option 4: "Cancel validation"
Validation Checklist
1. Plugin Structure
Verify required directories and files exist:
# Required: plugin.json
ls plugins/{name}/.claude-plugin/plugin.json
# Required: README.md
ls plugins/{name}/README.md
# At least one of these must exist:
ls plugins/{name}/agents/ # Agent definitions
ls plugins/{name}/commands/ # User-facing commands
ls plugins/{name}/skills/ # Skill implementations
Pass criteria: plugin.json + README.md + at least one content directory
2. Plugin.json Validation
Read and validate plugins/{name}/.claude-plugin/plugin.json:
Required fields:
name- Plugin identifier (string, non-empty)version- Semantic version (string, format: X.Y.Z)description- Plugin description (string, non-empty)
Optional but recommended:
author- Author information (object withname)license- License identifier (string, e.g., "Apache-2.0")keywords- Search keywords (array of strings)repository- GitHub repository URL
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.
- 7d ago First seen · 204 lines · 0 tokens per session scan A 067d212b36be
gh-plugin is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,420 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.
paper-trail-review
Review and arbitrate problematic references (cascade-exhausted, unresolved UID, awaiting OCR). Generates an up-to-date report, walks through cases by category, and applies arbitration decisions to the registry.
paper-trail-decide
Inspect a single reference in detail (identity, PDF status, acquisition history with verdicts, citation context in vault, state transitions) and decide its fate. Offers actionable decisions based on the ref's current state.
paper-trail-new-paper
Start writing an academic paper (IMRaD structure) on a topic, with anti-hallucination citation verification at every step. Builds on existing audited SOTAs.
paper-trail-registry-cleanup
Nettoyage historique du registre des fiches bibliographiques (les 900 fiches existantes). Cible les vieilles fiches mal nommées (0000, untitled) ET les duplicates avec suffixes numériques (foo2020bar2, 234) qui sont des artefacts de runs INGEST passés. Délègue les décisions au sub-agent textbook-resolver. Les merge…
paper-trail-cascade
Acquire PDFs via the 8-source cascade (11 with opt-in extended sources) for a single ref by slug, or a batch filtered by state. Validates page 1 anti-homonymy on each download.