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.
git clone --depth 1 https://github.com/jonase47/ccprWrote 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/jonase47/ccpr/p3-ux-darkmode)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-ux-darkmode"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-ux-darkmode/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/jonase47/ccpr/p3-ux-darkmode"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-ux-darkmode.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.00836 |
| Opus 5.5 | $0.00000 | $0.00334 |
| Sonnet 5.5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
p3-ux-darkmode 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-ux-darkmode – Dark Mode Color Strategy
Defines the color strategy for dark mode with semantic colors and toggle mechanism.
Argument: $ARGUMENTS = [Toggle mechanism, e.g. "System Preference", "Toggle", "both"]
If provided: Use the mechanism as the specification. If not provided: Recommend the most suitable mechanism.
Prerequisites
- Wireframes from
/p3-ux-wireframesavailable
Agent
- Type: ux-designer
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From UX_CONCEPT.md: Wireframes (short list of screens and elements)
- Dark mode requirement and color blindness note
Prompt Template
Goal: Define dark mode color strategy. Toggle: $ARGUMENTS
Context: [inline from UX_CONCEPT.md, CLAUDE.md]
Output Format:
- Semantic colors: Table | Token | Light | Dark | Usage |
- Critical components: which ones need special dark mode treatment?
- Toggle mechanism: description (1-2 sentences)
Constraints:
- ONLY color strategy and toggle mechanism
- NO wireframes, NO accessibility analysis
- Semantic tokens instead of hex values in design
- Max. 12 color tokens
- Color-blindness-friendly (blue/orange instead of red/green)
Orchestrator Checkpoint
- All wireframe elements covered by tokens?
- Color blindness requirement considered?
Write Detail File
Write the result to docs/architecture/DARKMODE.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: ux-darkmode
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Semantic Colors (the token/light/dark/usage table), ## Critical Components, ## Toggle Mechanism.
Update Sub-Index
Update docs/architecture/UX_CONCEPT.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[DARKMODE.md](DARKMODE.md)with statuscomplete. - Lift the toggle decision into Key Decisions of the sub-index.
- Do not edit
ARCHITECTURE.mddirectly.
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 Changed 68bf3af6bacb
- 1mo ago First seen · 87 lines · 0 tokens per session scan A 5816d22e2645
p3-ux-darkmode is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 836 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-09-03.
Other commands, from other repositories
prototype
Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery.
style-guide
Generate a style guide with design tokens, type scale, spacing, components, and Tailwind or CSS config.
design-intent
Guided UI/visual development with structured exploration, architecture design, and quality review.
stitch-generate
Full Stitch pipeline — author prompts, generate screens via MCP, fetch images and code.
stitch-setup
Guided setup and verification of Stitch MCP server connection.
bliss
Create distinctive, human-centered frontend interfaces. Use for UI components, pages, and applications with bold aesthetics and WCAG compliance.