Borrowing it
Nothing to install: this file belongs to russellbrenner/jurisd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/russellbrenner/jurisd/main/AGENTS.mdgit clone --depth 1 https://github.com/russellbrenner/jurisdWrote 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/russellbrenner/jurisd/agents-md)<a href="https://agentmods.dev/instructions/russellbrenner/jurisd/agents-md"><img src="https://agentmods.dev/badge/instructions/russellbrenner/jurisd/agents-md/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/instructions/russellbrenner/jurisd/agents-md"><img src="https://agentmods.dev/badge/instructions/russellbrenner/jurisd/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00625 | $0.00625 |
| Opus 5.5 | $0.00250 | $0.00250 |
| Sonnet 5.5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
jurisd 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 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions for jurisd
Purpose
jurisd is a source-backed Australian legal research and provenance instrument over a governed command surface. It exposes legal research capabilities through MCP, CLI, and future TUI adapters.
Do not describe jurisd as a chatbot, oracle, AI companion, or autonomous legal advice system.
Current foundation architecture
Current files:
src/server.tsregisters the current MCP tool surface.src/cli.tshandles CLI entry before the server starts.
Foundation PR 1 is introducing planned command-surface governance files:
src/commands/types.tswill define command contract and authority metadata types.src/commands/contracts.tswill provide the command contract registry for CLI/docs/future adapters.docs/MCP-COMPATIBILITY.mdwill record the MCP compatibility set once present.
Command contract rule
Foundation PR 1 is introducing the command contract registry. Once present, add commands once through that registry.
Every public command contract needs:
- stable command id
- synopsis
- summary
- arguments
- flags
- stdin mode
- output modes
- exit codes
- validation schema reference or adapter mapping
- stability level
- side-effect class
- terminal safety policy
- capability gates
- result contract
Adapter-specific metadata is required when that adapter is enabled.
Until the registry exists, command surface changes must preserve MCP compatibility and update tests and docs together.
MCP surface rule
MCP tools are curated. Do not expose operator, install, update, destructive, filesystem-write, or network-write commands over MCP unless a later authority decision explicitly permits it.
Existing MCP tool names are compatibility-sensitive. Update docs/MCP-COMPATIBILITY.md once present. Before then, update the MCP tool-surface tests before changing the tool surface.
Security invariants
- No secrets in code, docs, logs, tests, command output, or examples.
- No shell execution with user-controlled strings.
- Treat CLI args, TUI input, MCP input, provider output, source text, filenames, URLs, and completion candidates as untrusted.
- Keep stdout for primary output and stderr for diagnostics.
- JSON and NDJSON output must not contain terminal decoration.
- Terminal output must strip or neutralise unsafe ANSI, OSC, control characters, and bidi controls when it renders untrusted text.
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 · 85 lines · 625 tokens per session scan A b34e14af280b
jurisd AGENTS.md is an instructions file published in the GitHub repository russellbrenner/jurisd (40 stars, last pushed yesterday), licensed Apache-2.0. It adds 625 tokens to every session, about $0.0025 per session on Opus 5.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-30.
Other instructions, from other repositories
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.