CCG is a command-line workflow engine that coordinates Claude, Codex, Gemini, and other models as specialized collaborators on coding tasks. It is used to analyze requests, choose a strategy, delegate work to model-specific roles, and combine their results. The catalogue entries provide the skills, commands, agents, and plugin that implement this workflow.
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 skills add fengshao1227/ccg-workflow --skill quietergit clone --depth 1 https://github.com/fengshao1227/ccg-workflowWrote 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/fengshao1227/ccg-workflow/quieter)<a href="https://agentmods.dev/skills/fengshao1227/ccg-workflow/quieter"><img src="https://agentmods.dev/badge/skills/fengshao1227/ccg-workflow/quieter/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/skills/fengshao1227/ccg-workflow/quieter"><img src="https://agentmods.dev/badge/skills/fengshao1227/ccg-workflow/quieter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01103 |
| Opus 5 | $0.00023 | $0.00551 |
| Sonnet 5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
quieter 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- quieter — 100% identical, 2 lines differ
- quieter — 100% identical, 2 lines differ
- quieter — 97% identical, 10 lines differ
- quieter — 97% identical, 7 lines differ
- quieter — 97% identical, 10 lines differ
- quieter — 97% identical, 32 lines differ
- quieter — 97% identical, 7 lines differ
- quieter — 91% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reduce visual intensity in designs that are too bold, aggressive, or overstimulating, creating a more refined and approachable aesthetic without losing effectiveness.
MANDATORY PREPARATION
Invoke /frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first.
Assess Current State
Analyze what makes the design feel too intense:
-
Identify intensity sources:
- Color saturation: Overly bright or saturated colors
- Contrast extremes: Too much high-contrast juxtaposition
- Visual weight: Too many bold, heavy elements competing
- Animation excess: Too much motion or overly dramatic effects
- Complexity: Too many visual elements, patterns, or decorations
- Scale: Everything is large and loud with no hierarchy
-
Understand the context:
- What's the purpose? (Marketing vs tool vs reading experience)
- Who's the audience? (Some contexts need energy)
- What's working? (Don't throw away good ideas)
- What's the core message? (Preserve what matters)
If any of these are unclear from the codebase, Ask the user using AskUserQuestion.
CRITICAL: "Quieter" doesn't mean boring or generic. It means refined, sophisticated, and easier on the eyes. Think luxury, not laziness.
Plan Refinement
Create a strategy to reduce intensity while maintaining impact:
- Color approach: Desaturate or shift to more sophisticated tones?
- Hierarchy approach: Which elements should stay bold (very few), which should recede?
- Simplification approach: What can be removed entirely?
- Sophistication approach: How can we signal quality through restraint?
IMPORTANT: Great quiet design is harder than great bold design. Subtlety requires precision.
Refine the Design
Systematically reduce intensity across these dimensions:
Color Refinement
- Reduce saturation: Shift from fully saturated to 70-85% saturation
- Soften palette: Replace bright colors with muted, sophisticated tones
- Reduce color variety: Use fewer colors more thoughtfully
- Neutral dominance: Let neutrals do more work, use color as accent (10% rule)
- Gentler contrasts: High contrast only where it matters most
- Tinted grays: Use warm or cool tinted grays instead of pure gray—adds sophistication without loudness
- Never gray on color: If you have gray text on a colored background, use a darker shade of that color or transparency instead
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 · 103 lines · 47 tokens per session scan A 635cd9146482
quieter is a skill published in the GitHub repository fengshao1227/ccg-workflow (5,881 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 1,103 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
absolute-ui
Build polished, intentional UIs with concrete CSS/Tailwind values — typography, color, layout, spacing, dark mode, accessibility, animations, components. Encodes specific, opinionated rules with exact values, not vague advice. Covers buttons, cards, forms, tables, navigation, dashboards, landing pages, onboarding, and…
ve-terminal-mono
OpenDesign from the CLI: driving the full design workflow with the od command — scripted, composable, agent-ready. Built as a decision-grade AI literacy deck for developers, power users.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-obsidian-claude-gradient
OpenDesign's enterprise AI-adoption brief: local-first agents at work, the risk controls, the ROI, and the rollout plan. Built as a decision-grade AI literacy deck for leadership, IT, security.
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
create-openbitfun-cinematic-wallpaper-skin
Apply the cinematic animated-wallpaper style recipe to a OpenBitFun Appearance skin. Use after loading the parent create-openbitfun-skin Skill when the user provides animated character artwork and wants a host-managed video background, source-derived glass materials, image-led cards, illustrated dialogs, reproducible…