jig

A setup tool that asks which mistakes recur in your repository and configures checks to catch them, such as a linter, type checker, tests, or continuous integration (CI).

In plain words
What is it for?
Use it to define repository-specific safeguards and test whether each check catches an intentionally planted mistake.
Why use it?
It turns recurring bugs and code-quality problems into checks that can be run automatically, while requiring your approval before changes are added.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add V-Songbird/slag
agentmods
npx agentmods add plugins/v-songbird/slag/jig
Clone the repo
git clone --depth 1 https://github.com/V-Songbird/slag

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

jig 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.

jig/.claude-plugin/plugin.json · 13 lines

What it actually says

{
  "name": "jig",
  "description": "Interviews you about the mistakes that keep landing in your repo, then sets up what catches them: your linter, type checker, test runner, CI, and checks written for your codebase. Every check must catch a planted violation before it counts as coverage, and nothing lands you did not approve.",
  "license": "MIT",
  "author": {
    "name": "Victor Villegas",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/V-Songbird/slag/tree/main/jig",
  "repository": "https://github.com/V-Songbird/slag",
  "keywords": ["guardrails", "checks", "ci", "pre-commit", "hooks", "tests", "safety", "review", "interview"]
}
Changes

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.

  1. 2d ago First seen · 13 lines scan A 5640cd5b0db8

Subscribe to this mod's changes

jig is a plugin published in the GitHub repository V-Songbird/slag (2 stars, last pushed 3d ago), 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.