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.
npx agentmods add instructions/0x0w1/jig/claude-mdgit clone --depth 1 https://github.com/0x0w1/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/instructions/0x0w1/jig/claude-md)<a href="https://agentmods.dev/instructions/0x0w1/jig/claude-md"><img src="https://agentmods.dev/badge/instructions/0x0w1/jig/claude-md.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.02383 | $0.02383 |
| Opus 5 | $0.01192 | $0.01192 |
| Sonnet 5 | $0.00477 | $0.00477 |
| Haiku 4.5 | $0.00238 | $0.00238 |
Grade A, and why
jig CLAUDE.md 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.
This is a copy
94% identical to jig AGENTS.md — 45 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Rules
Use these repo-scoped Claude Code skills:
- Repository setup/sync:
github-syncfrom.claude/skills/github-sync/SKILL.md. - Release:
github-releasefrom.claude/skills/github-release/SKILL.md. - Ordinary implementation tasks targeting
develop:develop-task-flowfrom.claude/skills/develop-task-flow/SKILL.md. - Urgent fix for a released defect:
hotfix-flowfrom.claude/skills/hotfix-flow/SKILL.md. - README writing/updating:
readmefrom.claude/skills/readme/SKILL.md. - jig project installation and GitHub profile setup:
jig-setupfrom.claude/skills/jig-setup/SKILL.md. - jig installation updates:
jig-updatefrom.claude/skills/jig-update/SKILL.md. - jig installation diagnostics:
jig-doctorfrom.claude/skills/jig-doctor/SKILL.md. - Repository branch and file cleanup:
repo-hygienefrom.claude/skills/repo-hygiene/SKILL.md. - Procedure conformance audit of the history:
conformance-auditfrom.claude/skills/conformance-audit/SKILL.md. - Version grading rubric:
version-rubricfrom.claude/skills/version-rubric/SKILL.md. - Project type scan and rubric recommendation:
rubric-scanfrom.claude/skills/rubric-scan/SKILL.md.
Repository Model
mainanddevelopare protected against force pushes and deletion; direct pushes are allowed.- Work branches start from
origin/develop:feature/<slug>,fix/<slug>,chore/<slug>. - A finished task is squash-merged into
developlocally and pushed. There are no pull requests. - A release promotes
developtomainwith a fast-forward push (git push origin develop:main), then creates thevX.Y.Ztag and GitHub release from the CLI. - Release notes are written by the agent from the commits in the release range; there is no release-drafter and there are no release labels.
Terminology
- jig product means the behavior and payload delivered to users: installed skills, installer/update behavior, generated
dist/, plugin hooks, and state created in installed repositories. - jig source repository means this repository where the jig product is developed. Repo-local instructions, validation, project plans, and contributor tooling belong to this scope unless they are deliberately added to the product payload.
- jig-managed project means an external repository where jig is installed and used. Its clone-local hooks,
.jig/files, Git config, and GitHub settings are managed-project state. - Avoid “this project” or “the current project” when the distinction affects implementation. Say jig product, jig source repository, or jig-managed project explicitly.
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.
- 2d ago Changed · +6 lines · +314 tokens per session 0b62f9221022
- 6d ago First seen · 88 lines · 2,069 tokens per session scan A c9a9237296f3
jig CLAUDE.md is an instructions file published in the GitHub repository 0x0w1/jig (5 stars, last pushed 2d ago), licensed MIT. It adds 2,383 tokens to every session, about $0.0119 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to jig AGENTS.md, differing in 45 lines, and is treated as a copy.
Other instructions, from other repositories
my-git AGENTS.md
Instructions for xirong/my-git, covering agents.md, 仓库结构, 改动后必须验证, 内容规则 and 禁止操作.
watchfire CLAUDE.md
Instructions for watchfire-io/watchfire, covering watchfire - development guide, what is watchfire?, source of truth, task-completion lifecycle (v7.0 relay) and telegram bridge (v10.0 torch).
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.