Borrowing it
Nothing to install: this file belongs to b1rdmania/ghostclaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/b1rdmania/ghostclaw/main/.claude/skills/design/commands/init.mdgit clone --depth 1 https://github.com/b1rdmania/ghostclawWrote 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/commands/b1rdmania/ghostclaw/init)<a href="https://agentmods.dev/commands/b1rdmania/ghostclaw/init"><img src="https://agentmods.dev/badge/commands/b1rdmania/ghostclaw/init/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/b1rdmania/ghostclaw/init"><img src="https://agentmods.dev/badge/commands/b1rdmania/ghostclaw/init.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01987 |
| Opus 5.5 | $0.00000 | $0.00795 |
| Sonnet 5.5 | $0.00000 | $0.00397 |
| Haiku 4.5 | $0.00000 | $0.00199 |
Grade A, and why
init 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 1mo 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-init - Initialize Design Configuration
Create project-level design configuration files (.design.json and .design.md) that combine design system rules with Impeccable best practices.
Purpose
The /design-init command sets up a two-layer design configuration for your project:
Layer 1: Design System Rules (.design.json)
- Fonts, colors, spacing, typography
- Project-specific design constraints
- Used for fast anti-pattern detection and normalization
Layer 2: Design Philosophy (.design.md)
- Project context and brand personality
- Design principles and guidelines
- UX writing voice and tone
- Used for deep design reviews and polish
Usage
/design-init [directory]
Arguments:
directory(optional): Project directory to initialize. Defaults to current directory.
Behavior
Interactive Setup
-
Check for existing config
- If
.design.jsonor.design.mdexists, ask to overwrite or merge
- If
-
Choose starting point
Initialize from: 1. Minimal starter (recommended for new projects) 2. Emergence example (brutalist aesthetic) 3. Velocity example (clean, modern) 4. Custom (guided setup) -
Create
.design.json- Based on chosen template
- User can customize fonts, colors, spacing
-
Create
.design.md- Project context template
- User fills in: project name, target audience, brand personality, design principles
-
Confirm
✓ Created .design.json ✓ Created .design.md Next steps: - Edit .design.md to add project context - Run /design-rules to view current config - Run /design-audit [file] to check compliance
Templates
Minimal Starter (.design.json)
{
"name": "Project Name",
"version": "1.0.0",
"fonts": {
"heading": "Inter",
"body": "Inter",
"mono": "JetBrains Mono"
},
"colors": {
"primary": "#000000",
"secondary": "#666666",
"background": "#FFFFFF",
"text": "#000000"
},
"spacing": {
"xs": "4px",
"sm": "8px",
"md": "16px",
"lg": "24px",
"xl": "32px",
"2xl": "48px"
},
"typography": {
"h1": { "size": "48px", "lineHeight": "1.2", "weight": "700" },
"h2": { "size": "36px", "lineHeight": "1.3", "weight": "700" },
"h3": { "size": "24px", "lineHeight": "1.4", "weight": "600" },
"body": { "size": "16px", "lineHeight": "1.6", "weight": "400" },
"small": { "size": "14px", "lineHeight": "1.5", "weight": "400" }
},
"rules": [
"Use design system fonts only",
"Use design system colors only",
"Use design system spacing scale only",
"Maintain WCAG AA contrast ratios (4.5:1 for text)"
]
}
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.
- 1mo ago First seen · 306 lines · 0 tokens per session scan A 564a76da21eb
init is a command published in the GitHub repository b1rdmania/ghostclaw (84 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,987 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 commands, from other repositories
find
Quick gallery search. Use when user runs /meigen:find with keywords to browse inspiration.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.