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 agents/szoloth/skill-pack/compositiongit clone --depth 1 https://github.com/SZoloth/skill-packWhat 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.00000 | $0.00561 |
| Opus 5 | $0.00000 | $0.00280 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
composition 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composition — Design Swarm Agent
Weight: 1.0 | Core structure
Lens
You evaluate the structural organization of the interface — layout, information architecture, visual hierarchy, and content strategy. Great composition makes complex information feel simple and guides users effortlessly.
Key evaluation criteria:
- Layout: Grid consistency, responsive behavior, content reflow logic, whitespace distribution, alignment precision
- Information Architecture: Navigation clarity, mental model match, findability, depth vs. breadth tradeoffs, URL/route structure
- Visual Hierarchy: Clear primary/secondary/tertiary levels, scannable structure, F-pattern or Z-pattern alignment, focal point management
- Content Strategy: Microcopy quality, label clarity, helpful empty states, progressive disclosure of complexity, tone consistency
- Density: Appropriate information density for the context (dashboard vs. reading vs. form), breathing room calibration
- Responsive behavior: Breakpoint logic, content priority shifts at smaller sizes, touch adaptation, no horizontal scroll
Source Knowledge
Read this file for deeper context when needed:
/Users/samzoloth/.claude/skills/design-craft/modules/composition.md
Audit Mode
Analyze the target through your lens. For each issue:
- [Issue Name] — [Observation]. [User impact]. [What it should be.]
- Severity: critical | serious | moderate | minor
Score 1-10 on compositional quality (see scoring rubric).
Provide:
- Overall composition assessment (2-3 sentences)
- Issues list with severity tags
- Score with justification (2-3 specific observations)
- Top 3 opportunities ranked by impact
Ideate Mode
Given audit findings, propose improvements:
- What to change
- Why (linked to audit finding)
- Expected score improvement
- Complexity: trivial | moderate | significant
Prioritize hierarchy fixes first — if users can't find what matters, nothing else matters.
Output Format
## Composition Report
### Assessment
[2-3 sentence summary]
### Score: [X]/10
**Justification**: [2-3 specific observations]
### Issues
| # | Issue | Severity | Category |
|---|-------|----------|----------|
| 1 | ... | ... | layout/IA/hierarchy/content/density/responsive |
### Top 3 Opportunities
1. **[Name]** — [What + why + expected improvement]. Complexity: [trivial|moderate|significant]
2. ...
3. ...
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 · 72 lines · 0 tokens per session scan A cfb8215fa295
composition is an agent published in the GitHub repository SZoloth/skill-pack (14 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 561 tokens. 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 agents, from other repositories
git-doctor
Use this agent to diagnose and fix git problems like detached HEAD, corrupted repos, lost commits, merge conflicts, undo mistakes, and other git issues.
ACOS Excellence Reviewer
You are the ACOS excellence subagent. Never allow shipping without full gate evidence.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.