agentmods.dev

create-domain-section

A workflow for adding a new knowledge section when an existing Agent Core or project structure does not cover a major topic.

In plain words
What is it for?
Use it to decide whether a new section belongs to agent rules, project knowledge, raw sources, or temporary output, then identify its proper location.
Why use it?
It helps keep new information organized without creating unnecessary sections or placing source documents in the wrong area.

Skill for Claude CodeCodex

11 2mo ago A scan 33 tokens original MIT
View the source file TheMuleA/codex-agent-core-template
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/themulea/codex-agent-core-template/create-domain-section
Any agent
npx skills add TheMuleA/codex-agent-core-template --skill create-domain-section
Clone the repo
git clone --depth 1 https://github.com/TheMuleA/codex-agent-core-template

Made for: Claude Code, Codex.

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 838 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.00033 $0.00838
Opus 5 $0.00016 $0.00419
Sonnet 5 $0.00007 $0.00168
Haiku 4.5 $0.00003 $0.00084

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

Security

Grade A, and why

create-domain-section 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/create-domain-section/SKILL.md · 72 lines

How it starts

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

create-domain-section

Назначение

Помогает аккуратно добавлять новые разделы без самовольного разрастания структуры.

Когда использовать

  • Появился новый крупный домен знаний.
  • Существующих разделов Agent Core или active project layer недостаточно.
  • Пользователь передал материал, который требует отдельного раздела.
  • Нужен новый повторяемый business/project раздел для выбранного project layer.

Scope routing

Перед предложением раздела определить scope:

  • Agent Core section — относится к модели агента, protocols, skills, planning, work plans, reference sources.
  • Project section — относится к выбранному project layer: компания, роль, цели, продукты, продажи, CRM, рынок, конкуренты, маркетинг, управление, playbooks или новый business domain.
  • Raw/source section — относится к исходникам и должен жить в raw/, а не в content layer.
  • Output section — временный результат и не должен становиться постоянным разделом без отдельного решения.

Фактический project_id берётся из projects/index.md после выбора active project.

Target paths

  • Agent Core sections: agent/<section>/ only if это действительно часть постоянной агентской сущности.
  • Project sections: projects/<project_id>/<section>/.
  • Raw sources: raw/sources/<source-name>/ или другой согласованный raw path.
  • Output: output/.

Новые project roles or business domains должны создаваться внутри выбранного project layer, а не в Agent Core.

Процедура

  1. Объяснить, почему нужен отдельный раздел.
  2. Определить scope: Agent Core, active project, raw/source или output.
  3. Проверить, нельзя ли использовать уже существующий раздел.
  4. Предложить название папки и базовую структуру.
  5. Показать связи с уже существующими разделами.
  6. Указать, какие индексы нужно обновить.
  7. Сформировать предложение изменения через propose-file-change.
  8. Создать раздел только после подтверждения пользователя.
  9. После создания обновить релевантные index/hub files and logs.

Index updates

Для Agent Core section обычно проверить:

  • agent/index.md;
  • профильный index/hub в agent/model/, agent/protocols/, agent/planning.md, agent/work-plans/ или agent/skills-index.md;
  • agent/model/structure.md, если меняется сама структура Agent Core.

Read the full file on GitHub · 72 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 · 72 lines · 33 tokens per session scan A 98ee3db15ba4

Subscribe to this mod's changes

create-domain-section is a skill published in the GitHub repository TheMuleA/codex-agent-core-template (11 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 838 once invoked, about $0.0002 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.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens