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 liustack/vibemaster --skill shapinggit clone --depth 1 https://github.com/liustack/vibemasterWrote 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/liustack/vibemaster/shaping)<a href="https://agentmods.dev/skills/liustack/vibemaster/shaping"><img src="https://agentmods.dev/badge/skills/liustack/vibemaster/shaping/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/liustack/vibemaster/shaping"><img src="https://agentmods.dev/badge/skills/liustack/vibemaster/shaping.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.00206 | $0.01795 |
| Opus 5.5 | $0.00082 | $0.00718 |
| Sonnet 5.5 | $0.00041 | $0.00359 |
| Haiku 4.5 | $0.00021 | $0.00179 |
Grade A, and why
shaping 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shaping: from unformed intent to something actionable
Shaping converges an unformed intent into something the user can act on: a requirement spec, a solution design, a set of genuinely different candidates, a grounded call. The method is exclusion. Each round rules out part of what the deliverable could be, until what remains is small enough to act on.
Pay per gap, not per pipeline. Divergence and grilling are operators called when their gap blocks, never stages every request walks through.
When not to run
A request that already points at one thing (execute an existing spec, answer a question, deliver settled content) leaves nothing to exclude. Complete the original request directly. Zero questions, zero files, no mention of this skill. Life and career decisions are not this skill's work either. When it cannot be told whether this applies, it does not. A later message with a stronger signal can still enter.
A mixed request exempts only its execution items, never its question. When a request bundles build items with an undecided question whose answer changes what gets built, converge that question first (usually entering directly at 2→3), deliver the call with grounds, then continue the execution items. A majority of execution items is not a reason to skip the question.
A candidate the user brings is a candidate, not a decision. "Maybe just X" enters 2→3 to be judged alongside the alternatives. It does not close the gate.
Three working rules
- Output that excludes nothing is not progress. A pile of candidates excludes nothing. Same-family rewordings exclude nothing. A question whose answer would not change the deliverable excludes nothing.
- Every exclusion carries its grounds, and what new evidence would reopen it. When grounds are missing, do not fake a recommendation. Recommend the smallest action that buys the evidence.
- Any exclusion can be reopened by new evidence, and reopening beats refining. When the frame is wrong, stop decorating inside it.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 78 lines · 206 tokens per session scan A 3eda633d459f
shaping is a skill published in the GitHub repository liustack/vibemaster (13 stars, last pushed 2mo ago), licensed MIT. It adds 206 tokens to every session and 1,795 once invoked, about $0.0008 per session on Opus 5.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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.