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/ramboz/jigWrote 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/plugins/ramboz/jig/marketplace)<a href="https://agentmods.dev/plugins/ramboz/jig/marketplace"><img src="https://agentmods.dev/badge/plugins/ramboz/jig/marketplace/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/plugins/ramboz/jig/marketplace"><img src="https://agentmods.dev/badge/plugins/ramboz/jig/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jig marketplace 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.
What it actually says
{
"name": "jig",
"owner": {
"name": "ramboz"
},
"plugins": [
{
"name": "jig",
"source": {
"source": "git-subdir",
"url": "https://github.com/ramboz/jig.git",
"path": "hosts/claude"
},
"description": "Spec-driven, review-enforced, hook-gated AI-native development workflow for Claude Code"
}
]
}
The plugins it lists here
This marketplace lists 2 plugins kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 18 lines scan A 99b99b31b64d
jig marketplace is a plugin published in the GitHub repository ramboz/jig (7 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
codeweaver
ctx
skillrx
Security scanner for AI agent skills and plugins (Claude Code, Codex, Cursor, and 40+ more).
supergraph
Evidence-gated AI coding workflow: scan → analyze → plan → TDD → execute → fix → verify → review, powered by Codebase Memory MCP >= 0.10.8,<0.11.0 with optional Serena LSP intelligence, 7 specialized subagents, and native Rust CDP browser/API automation. Includes blast-radius planning, test/cycle gates, independent…
voice-calibration-marketplace
Plugin marketplace listing 1 plugin: voice-calibration-plugin.
voice-calibration-plugin
Learns your personal writing and speaking style through interactive prompts, then generates a reusable voice profile so AI can write like you.