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 agentmods add skills/anastasiyaw/codex-claude-code-config/layer-newnpx skills add AnastasiyaW/codex-claude-code-config --skill layer-newgit clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-configWrote 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/anastasiyaw/codex-claude-code-config/layer-new)<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/layer-new"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/layer-new.svg" alt="Measured on agentmods" 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.00150 | $0.01877 |
| Opus 5 | $0.00075 | $0.00938 |
| Sonnet 5 | $0.00030 | $0.00375 |
| Haiku 4.5 | $0.00015 | $0.00188 |
Grade A, and why
layer-new 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 6d 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/layer-new -- scaffold a project layer
Creates docs/layers/<layer-name>/ with the full template structure
defined by principle 28.
When to use
- Starting to track a new bounded concern in a long-running project
- Refactoring sprawling cross-cutting code into a documented layer
- Onboarding a new team member who needs the layer map
When NOT to use
- One-off scripts or pet projects with <5 features (overhead not justified)
- Layer name describes a directory (
srcis not a layer) - The "layer" is actually one feature in disguise -- use
/feature-newinside an existing layer instead
Arguments
/layer-new <layer-name> [--purpose "..."] [--principles P-NN,P-MM]
<layer-name>-- kebab-case, single word preferred. Examples:security,data,image-processing,observability.--purpose-- one-sentence purpose. If omitted, prompt the user.--principles-- comma-separated Tier 1 principle IDs that govern this layer (e.g.P-02,P-21). If omitted, leave placeholder in README.
Direction (what to do, in order)
Step 1 -- Verify environment
Check the current working directory:
- Is it a git repository? Run
git rev-parse --show-toplevel. If not, ask the user whether to initialize one (offergit init+ private GitHub repo per global rule). - Does
docs/exist? If not, create it. - Does
docs/layers/README.mdexist? If not, copy from<claude-code-skills-checkout>/templates/kb-skeleton/docs/layers/README.md. - Check if
docs/layers/<layer-name>/already exists. If yes, stop with a message -- do not overwrite. Suggest/feature-new <layer> <slug>instead.
Step 2 -- Validate layer name
- Must be lowercase kebab-case (
[a-z][a-z0-9-]*). - Must not start with
_(reserved for templates). - Must not be a generic file-system name (
src,tests,docs,build). - If invalid, refuse with a clear message and a suggested fix.
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.
- 6d ago First seen · 193 lines · 150 tokens per session scan A cf6513f0cafe
layer-new is a skill published in the GitHub repository AnastasiyaW/codex-claude-code-config (149 stars, last pushed today), licensed MIT. It adds 150 tokens to every session and 1,877 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
ai-content-filter
Professional Ai Content Filter Expert skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
ai-engineer
Professional Ai Engineer skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
ai-product-manager
Professional Ai Product Manager Expert skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
embedding-architect
Professional Embedding Architect skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
eval-harness
Professional Eval Harness Expert skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.
feature-engineer
Professional Feature Engineer skill. Integrate LLM API workflows, safe system prompt guidelines, and agentic workflows.