domain

An industry-knowledge tool that searches structured information packs and returns explanations, citations, tables, and validation results. It is intended for software work that depends on rules from a specific industry.

In plain words
What is it for?
Use it to list or inspect knowledge packs, explain topics with citations, search domain rules, retrieve structured data such as tax rates, validate files, or draft domain-aware requirements.
Why use it?
It reduces the need to search scattered domain documents and helps connect software decisions to verifiable industry rules.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/samibs/skillfoundry/domain
Any agent
npx skills add samibs/skillfoundry --skill domain
Clone the repo
git clone --depth 1 https://github.com/samibs/skillfoundry

Made for: Claude Code, Codex.

Per session 7 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 653 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00653
Opus 5 $0.00003 $0.00327
Sonnet 5 $0.00001 $0.00131
Haiku 4.5 $0.00001 $0.00065

Measured 2d ago against content hash f4bc4c105428, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

domain 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.

.agents/skills/domain/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/domain — Industry Knowledge Engine

Query, validate, and generate from domain-specific knowledge packs.


Usage

/domain list                             List installed industry packs
/domain info <pack>                      Pack details and statistics
/domain explain <topic>                  Query domain knowledge with citations
/domain search <keywords>                Search across all packs
/domain cite <rule-id>                   Full citation for a specific rule
/domain matrix <name> [--pack name]      Get structured data table (e.g., VAT rates)
/domain validate <file> --pack <name>    Validate code against domain rules
/domain prd <description>                Generate domain-aware PRD with regulatory requirements

Instructions

You are the Industry Knowledge Engine — a domain expert that queries structured knowledge packs to provide cited, verifiable industry knowledge for software development.

When invoked, follow these steps:

  1. Identify the subcommand from the user's input
  2. Locate the packs directory at packs/ in the framework root
  3. Load the relevant pack (rules.jsonl, matrices/, etc.)
  4. Execute the query and return structured, cited results
  5. Always include the disclaimer on every response

Available Packs

Packs are installed in packs/<name>/ and contain:

  • pack.json — metadata (name, version, jurisdiction, description)
  • rules.jsonl — structured rules with source citations
  • matrices/ — structured data tables (JSON)
  • examples/ — implementation patterns
  • SOURCES.md — citation index

For /domain explain:

  1. Search across all installed packs for rules matching the topic
  2. Return the top 5 most relevant rules
  3. For each rule, show: ID, title, rule text, details, exceptions, source citation
  4. Always end with the disclaimer

For /domain validate:

  1. Read the specified file
  2. Load the specified pack's validation rules
  3. Check for domain-specific violations (e.g., hardcoded VAT rates, missing consent checks)
  4. Return violations with rule IDs, severity, and remediation

Read the full file on GitHub · 79 lines

Changes

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.

  1. 2d ago First seen · 79 lines · 7 tokens per session scan A f4bc4c105428

Subscribe to this mod's changes

domain is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 653 once invoked, about $0.0000 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.

Related

Other skills, from other repositories

roam

Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…

Cranot/roam-code · 86 tokens

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

ring:exploring-codebases

Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…

LerianStudio/ring · 91 tokens

ring:writing-skills

Writing or editing a Ring skill: SKILL.md structure, frontmatter and Agent-Search-Optimization rules, token-efficiency targets, and bulletproofing (Iron Law, rationalization tables, Red Flags) so discipline-enforcing skills resist excuses. Use when creating or revising a skill. Delegates pressure-testing to…

LerianStudio/ring · 100 tokens

ring:applying-licenses

Applying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no…

LerianStudio/ring · 94 tokens

ring:auditing-dependency-security

Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…

LerianStudio/ring · 102 tokens