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/etr/groundwork/split-architecturenpx skills add etr/groundwork --skill split-architecturegit clone --depth 1 https://github.com/etr/groundworkWhat 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 | $0.00027 | $0.01854 |
| Opus 5 | $0.00014 | $0.00927 |
| Sonnet 5 | $0.00005 | $0.00371 |
| Haiku 4.5 | $0.00003 | $0.00185 |
Grade A, and why
split-architecture 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Split Architecture Skill
Converts a single-file architecture document ({{specs_dir}}/architecture.md) into a directory-based format ({{specs_dir}}/architecture/) for better organization and targeted context loading.
When to Use
- Automatically by
design-architectureandsource-architecture-from-codewhen the single-file architecture doc crosses 500 lines or 10 decision records (sections matching### DR-\d+) - Manually when the user invokes
/split-architecture
Step 0: Resolve Project Context
- Monorepo check: Does
.groundwork.ymlexist at the repo root?- If yes → Is
{{project_name}}non-empty?- If empty → Invoke
Skill(skill="groundwork:select-project")to select a project, then restart this skill. - If set → Project is
{{project_name}}, specs at{{specs_dir}}/.
- If empty → Invoke
- If no → Continue (single-project repo).
- If yes → Is
- Proceed with the resolved project context.
Step 1: Validate Preconditions
- Check single file exists:
{{specs_dir}}/architecture.mdmust exist- If missing → output "No single-file architecture doc found at
{{specs_dir}}/architecture.md. Nothing to split." and stop.
- If missing → output "No single-file architecture doc found at
- Check directory does NOT exist:
{{specs_dir}}/architecture/must not already exist- If it exists → output "Architecture doc is already in directory format at
{{specs_dir}}/architecture/. Nothing to do." and stop.
- If it exists → output "Architecture doc is already in directory format at
- Read the file and count lines and decision records (sections matching
^### DR-\d+).
Step 2: Split the File
Parse the single-file architecture doc into sections and write each to its own file under {{specs_dir}}/architecture/.
Directory Structure
{{specs_dir}}/architecture/
├── _index.md # Header, metadata
├── 01-executive-summary.md # Section 1: Executive Summary
├── 02-architectural-drivers.md # Section 2: Architectural Drivers
├── 03-system-overview.md # Section 3: System Overview
├── 04-components/ # Section 4: One file per component
│ ├── _index.md # Section 4 header ("## 4) Component Details")
│ └── <component-slug>.md # e.g., cli.md, query-router.md
├── 05-data.md # Section 5: Data Architecture
├── 06-integration.md # Section 6: Integration Architecture
├── 07-security.md # Section 7: Security Architecture
├── 08-infrastructure.md # Section 8: Infrastructure & Deployment
├── 09-observability.md # Section 9: Observability
├── 10-cost-model.md # Section 10: Cost Model
├── 11-decisions/ # Section 11: One file per DR
│ ├── _index.md # Section 11 header ("## 11) Decision Records")
│ └── DR-NNN.md # e.g., DR-001.md, DR-015.md
├── 12-open-questions.md # Section 12: Open Questions & Risks
└── 13-appendices.md # Section 13: Appendices
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.
- 2d ago First seen · 146 lines · 27 tokens per session scan A 9cb34fbb9b96
split-architecture is a skill published in the GitHub repository etr/groundwork (42 stars, last pushed 20d ago), licensed MIT. It adds 27 tokens to every session and 1,854 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…