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 skills add russellbrenner/jurisd --skill jurisd-researchgit 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/skills/russellbrenner/jurisd/jurisd-research)<a href="https://agentmods.dev/skills/russellbrenner/jurisd/jurisd-research"><img src="https://agentmods.dev/badge/skills/russellbrenner/jurisd/jurisd-research/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/skills/russellbrenner/jurisd/jurisd-research"><img src="https://agentmods.dev/badge/skills/russellbrenner/jurisd/jurisd-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 50 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00133 | $0.02344 |
| Opus 5 | $0.00067 | $0.01172 |
| Sonnet 5 | $0.00027 | $0.00469 |
| Haiku 4.5 | $0.00013 | $0.00234 |
Grade A, and why
jurisd-research 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 11d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jurisd: Australian/NZ legal research
jurisd is an MCP server for AU/NZ legal research. It searches AustLII, fetches
full-text judgments, formats AGLC4 citations, manages a local citation cache +
bibliography, and serves offline recall from installed data modules. There are
12 tools; operation variants are picked via a mode/op/action/by
discriminator, not separate tools.
Core rule: local first, live as fallback
When data modules are installed (check with list_data_modules), prefer the offline
tools for deterministic, citable, no-network answers. Fall through to live tools when
the module misses or no module is installed. The local tools return a typed not-found
so you can tell a genuine miss from an error.
| Need | Local first (offline) | Live fallback |
|---|---|---|
Read a specific provision (s 18) |
get_provision |
search_legislation → fetch_document_text |
| Act outline / structure | get_act_structure |
search_legislation → fetch_document_text |
| Who cites this case | find_citing |
— (local module graph only) |
| Concept / natural-language recall | semantic_search_local |
search_cases / search_legislation |
Always check list_data_modules once at the start of a research session so you know
which layer to lead with. Every local answer carries metadata.source = "local_module"
with module name, version, and snapshot date; mind the staleness advisory.
The 12 tools
Live research
search_cases— NL case-law search across all AU/NZ jurisdictions (AustLII, authority-ranked).method: auto/title/phrase/all/any/near/boolean;jurisdiction;sortByauto/relevance/date;offsetfor pagination.search_legislation— same controls for legislation (methodaddslegis).fetch_document_text— full text from an AustLII URL (HTML, PDF via pdf-parse). PassciteKeyto also save a local source copy + freshness headers.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 153 lines · 133 tokens per session scan A c82f64d57eb4
jurisd-research is a skill published in the GitHub repository russellbrenner/jurisd (35 stars, last pushed yesterday), licensed Apache-2.0. It adds 133 tokens to every session and 2,344 once invoked, about $0.0007 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-30.
Other skills, from other repositories
graphify
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community…
sciatlas-idea-generate
Use only the current SciAtlas multi-step idea-generation workflow (sciatlasideagen) to take a novice user from zero setup to final literature-grounded research idea seeds, including setup, registration guidance, workflow configuration, KG retrieval, artifact reading, novelty checking, and synthesis. Trigger when the…
sciatlas-literature-review
Use only the current SciAtlas literature-review workflow (literaturereviewpipeline) to take a novice user from zero setup to a final evidence-grounded survey outline, paper map, or literature review, including setup, registration guidance, workflow configuration, SciAtlas backend retrieval, artifact reading, and…
sciatlas-idea-evaluate
Use only the current SciAtlas automated review workflow (reviewpipeline) to take a novice user from zero setup to a final automated review of a research idea or paper, including setup, registration guidance, workflow configuration, retrieval, artifact reading, and synthesis. Trigger when the user asks whether an idea…
sciatlas-quick-paper-search
Use only SciAtlas search-papers to take a novice user from zero setup to a final small evidence-backed paper search result, including setup, registration guidance, configuration, retrieval, artifact reading, and summary. Trigger when the user wants a quick paper check, first-pass literature evidence, a retrieval smoke…
sciatlas-idea-grounding
Use only SciAtlas search-papers to take a novice user from zero setup to final prior-art grounding for a research idea, including setup, registration guidance, configuration, retrieval, artifact reading, and synthesis. Trigger when the user gives an idea and asks for similar work, differentiation evidence, related…