domain-model
Skill1 starsChanged 3 months agoMITView on GitHub
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- thoughtbot/rails-consultanttheir own version, first seen Nov 8, 2026
- mariomile/builder-ostheir own version, first seen Nov 1, 2026
- evelan-de/claude-code-pluginstheir own version, first seen Oct 17, 2026
- stevepolitodesign/skillstheir own version, first seen Oct 14, 2026
- tslateman/skillstheir own version, first seen Oct 11, 2026
- joelhooks/joelclawtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use codebase-design, tdd and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillcodebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
- +1 more from google
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- ayoubben18/ab-method★ 193same name
- joelhooks/joelclaw★ 66same name
- thoughtbot/rails-consultant★ 29same name
- stevepolitodesign/skills★ 10same name
- evelan-de/claude-code-plugins★ 3same name
- mariomile/builder-os★ 2same name
- mik2win/foureyes★ 2same name
- witi-projects/Skills★ 2same name
- tslateman/skills★ 1same name
- ltatarev/skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- enrichmentSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Run classify first to determine archetypes from recon data.
- Very specific: line 18
Run map-surfaces second to map detected infrastructure to attack surfaces.
- Very specific: line 19
Run profile third to generate the full domain profile report for dispatch decisions.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Domain Model
Overview
Application-agnostic domain archetype classification for bug bounty targets. Infers what the target application actually does based on recon data — classifying into archetypes (media platform, billing SaaS, marketplace, etc.) and mapping detected infrastructure to attack surfaces. This replaces "spray XSS/SQLi/SSRF everywhere" with archetype-driven, surface-prioritized testing.
This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.
Quick Reference
- Skill:
domain-model - Severity range:
info,low,medium - Required tools:
python3,pyyaml - Required prior skills:
recon(needssubdomains/subs.txt,live/live_full.csv,js/js_endpoints.txt) - Scope check: no intrusive operations in this skill — classification only.
- Redaction: classification, surface map, and domain profile artifacts are local-only and must be sanitized to redact target hostnames and identifiers before sharing; they are never committed and should stay covered by
.gitignore.
Workflow Selection
- Run
classifyfirst to determine archetypes from recon data. - Run
map-surfacessecond to map detected infrastructure to attack surfaces. - Run
profilethird to generate the full domain profile report for dispatch decisions. - Each workflow depends on the output of the previous.
Available Workflows
| Workflow | Purpose | Script paths | Primary outputs | Evidence |
classify | Classify target into domain archetypes from recon data | .claude/skills/domain-model/scripts/archetype_classifier.py | $OUTDIR/domain-model/archetypes.json | None (classification only) |
map-surfaces | Map detected infrastructure to attack surface taxonomy | .claude/skills/domain-model/scripts/surface_mapper.py | $OUTDIR/domain-model/surfaces.json | None (mapping only) |
profile | Generate full domain profile report with prioritized testing order | .claude/skills/domain-model/scripts/domain_report.py | $OUTDIR/domain-model/domain-profile.md | None (reporting only) |
Evidence Required
- This skill does not collect evidence directly. It produces classification artifacts.
- Archetype JSON: target, archetype list with confidence scores, supporting evidence strings.
- Surface JSON: target, detected surface list with confidence, auth requirements, intrusive levels.
- Domain profile: full markdown report with prioritized testing order and recommended skill loading sequence.
References
- Source of truth:
skill.yaml - Archetype definitions:
domain.yaml - Surface definitions:
surfaces.yaml - Runbooks:
runbooks/ - OWASP WSTG:
WSTG-INFO-01,WSTG-INFO-02,WSTG-INFO-03,WSTG-INFO-05,WSTG-INFO-06
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

