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/menta-guru-labs/jig/agents-mdgit clone --depth 1 https://github.com/menta-guru-labs/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/menta-guru-labs/jig/agents-md)<a href="https://agentmods.dev/instructions/menta-guru-labs/jig/agents-md"><img src="https://agentmods.dev/badge/instructions/menta-guru-labs/jig/agents-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.04215 | $0.04215 |
| Opus 5 | $0.02107 | $0.02107 |
| Sonnet 5 | $0.00843 | $0.00843 |
| Haiku 4.5 | $0.00421 | $0.00421 |
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 6d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 6d ago First seen · 380 lines · 4,215 tokens per session scan A 6fe7a67d2191
jig AGENTS.md is an instructions file published in the GitHub repository menta-guru-labs/jig (5 stars, last pushed 15d ago), licensed AGPL-3.0. It adds 4,215 tokens to every session, about $0.0211 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
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.
crystal AGENTS.md
Instructions for stravu/crystal, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
nextjs-skills CLAUDE.md
Instructions for mohamed-hossam1/nextjs-skills: All contribution rules — style, naming, file layout, verification — live in AGENTS.md. Read that first.
Warden-AI GEMINI.md
Gemini CLI instructions for rynald0cst0ltziam/Warden-AI, covering warden — context governance and verification layer, session start (important — do this first), layer 1: before starting work — context selection, layer 2: during work — tool output pruning and enforcement hooks (automatic).
agents-chat copilot-instructions.md
Copilot instructions for huanyingtianhe/agents-chat, covering copilot instructions, build & run, tests (playwright e2e), architecture and key components.
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).