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/ramboz/jig/agents-mdgit clone --depth 1 https://github.com/ramboz/jigWhat 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 | $0.02947 | $0.02947 |
| Opus 5 | $0.01473 | $0.01473 |
| Sonnet 5 | $0.00589 | $0.00589 |
| Haiku 4.5 | $0.00295 | $0.00295 |
Grade A, and why
jig AGENTS.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 3d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jig — AI-Native Dev Scaffold
The Codex skill pack that scaffolds AI-native development practices. We dogfood the workflow we build.
Hot Cache
Always-loaded primer, kept lean per spec 055/057 (orchestrator context × turns is the cost). This is an index: each bold term is a one-line claim + link; full definitions live in docs/memory/glossary.md + the lexicon and expand on demand via /jig:explain <term>. Update via /jig:memory-sync.
Project codenames / active work
- jig = this skill pack repo (the plugin itself).
- Branch routing —
mainis the sole active line: 1.x and the 2.0 multi-host work both shipped here (latest tagv2.10.0). The legacyv2branch is closed — don't route work to it. See docs/roadmap.md. - Active specs: none in-flight (088
/jig:orientskill shipped + closed; 091 bug-fix repository-closure shipped + closed). Bug-fix repository closure — ADR-0037 (Accepted) / spec 091 — two marker-keyed closure gates on the bug lifecycle;JIG_BUG_CLOSURE_GATE=0. Per-slice invariants live in the status-board Notes column. Long-horizon-autonomy bridge (oh-my-cli follow-on): spec 106 — autonomy governance plane & identity separation (ADR-0051, Accepted) is built; spec 105 — durable failure-quarantine jig-half (ADR-0050, Proposed) is still recorded, not built. servo halves live inramboz/servo(servo specs 023/024/025, ADR-0029/0030) — not yet built. See docs/specs/README.md. Deferred → docs/refinement-todo.md.
Key terms (one-line index — full defs via /jig:explain <term>)
- Configurable docs root — ADR-0033 / spec 084 —
layout.docs_rootin scaffold.json (defaultdocs);.= track-local adoption inside a larger repo; discovery sentinel-anchored; subtree push-mode refused. Read via_common/project_layout.py. - Subagent permission — In this jig project, the user explicitly permits Codex to use subagents when they materially help implementation, review, reconciliation, or coordination work.
- Lifecycle-family spine — ADR-0023 — spec-workflow / bug-fix / refactor share one C1–C7 gated-evidence spine; extract to
_common/lifecycle.pyonly at the thirdtransition. PARKED — don't re-propose the servo pluggable-oracle boundary (ADR-0022 C5) without a real eval case / servo spec 006 / a built consumer. - Closed-spec drift — ADR-0010 (supersedes ADR-0008) — closed records get
## Amendments; live prose corrected inline; new ADR for decision changes. Amending a record needs explicit owner approval (spec 102, issue #125): surface a canon-artifact conflict and stop; approving a behaviour ≠ authority to rewrite the record; read the whole criteria block before asserting a contradiction. - Spec-gate model — ADR-0011 —
jig-spec-gate.shis a deliberateness gate onconventions.md, not human-only enforcement; real control is out-of-band. - Security floor — ADR-0013 / spec 052 — 5-part scaffolded floor; defense-in-depth, not a firewall.
- Review-evidence gate — ADR-0014 (spec 045) —
transitiongates REVIEWED/RECONCILED/DONE on recorded verdict artifacts; bypassJIG_REVIEW_EVIDENCE_GATE=0. Sibling Lifecycle entry gate — ADR-0044 / spec 098 — fail-openPostToolUsenudge on an out-of-lifecycle source edit (no live claim held by this checkout); reads.jig/spec-ref(slice + 098-04bug=NNNarms) w/ a.gitignore/named-artifact boundary;JIG_ENTRY_GATE=0. Sibling Session git-freshness — ADR-0048 / spec 103 — fail-openSessionStarttime-zero nudge: fetches (timeout-guarded, best-effort) the integration base, warns whenHEADis behind before a stale premise forms; smart-target resolution (non-own@{upstream}elseorigin/main→origin/master; own-remote guard = base drift, not own-branch advancement);JIG_GIT_FRESHNESS=0. - Worktree-aware reservation — ADR-0015 / spec 051 —
newroutes on branch; off-main reserves via an ephemeral detached worktree at origin/main. - Context-cost discipline — spec 055 — cost ≈ orchestrator context × turns; delegate reads, keep the primer lean.
- Thin-orchestrator — spec 057 — turn count + peak context are the top cost knobs;
workflow.py session-plandispatches. - Token-usage tracking — spec 056 —
usage.py report <spec>per-spec token/$ totals; price via ccusage, never hand-rolled. - Slice-claim on working states — spec 049 / ADR-0045 —
transitionstampsclaimed_by:on WORKING states, releases on the pickup queue + terminal; blank ≠ free. - Solo→team re-detection — spec 050 — re-evaluates the team signal; nudges to bootstrap
people.md. - Vocabulary barrier / lexicon — spec 065 / ADR-0021 — on-demand jargon via
/jig:explain+ lexicon, off the hot path. - Status board — docs/specs/README.md, regenerated by
workflow.py status-board; Notes column preserved + load-bearing. - SPIDR, Vertical slice, Dumb zone, Reconciliation, Reframe (
/jig:reframe— ADR-0024), Tier 0/1/2, Hot Cache, Research note (docs/research/R-NNN, ADR-0054) — see glossary //jig:explain.
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.
- 3d ago First seen · 71 lines · 2,947 tokens per session scan A f665897b17be
jig AGENTS.md is an instructions file published in the GitHub repository ramboz/jig (6 stars, last pushed 3d ago), licensed MIT. It adds 2,947 tokens to every session, about $0.0147 per session on Opus 5. 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 instructions, from other repositories
frappe-agent AGENTS.md
Instructions for Dkm0315/frappe-agent, covering frappe agent instructions, core behavior, bench guidance, app provenance and erpnext guidance.
supergraph AGENTS.md
Instructions for datit309/supergraph, covering supergraph — mandatory workflows, skills, auto language detection, tiered workflow — pick the right tier first and full pipeline (tier 3).
frappe-agent copilot-instructions.md
Instructions for Dkm0315/frappe-agent: Treat this repository as Frappe, ERPNext, and Frappe ecosystem guidance for coding agents.
frappe-agent CLAUDE.md
Instructions for Dkm0315/frappe-agent: This repository contains Codex-native plugin assets plus portable Frappe, ERPNext, and Frappe ecosystem development guidance.
dev-flow AGENTS.md
Instructions for Innocent-children/dev-flow, covering dev flow repository instructions, authority, requirement scope, documentation and internationalization and product boundary.
codexhub AGENTS.md
Instructions for zpf2234/codexhub, covering codexhub contributor guide and project expectations.