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 SZoloth/skill-pack --skill shapinggit clone --depth 1 https://github.com/SZoloth/skill-packWrote 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/szoloth/skill-pack/shaping)<a href="https://agentmods.dev/skills/szoloth/skill-pack/shaping"><img src="https://agentmods.dev/badge/skills/szoloth/skill-pack/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/szoloth/skill-pack/shaping"><img src="https://agentmods.dev/badge/skills/szoloth/skill-pack/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.00030 | $0.05437 |
| Opus 5.5 | $0.00012 | $0.02175 |
| Sonnet 5.5 | $0.00006 | $0.01087 |
| Haiku 4.5 | $0.00003 | $0.00544 |
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.
This is a copy
100% identical to shaping — 147 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 594 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shaping Methodology
A structured approach for collaboratively defining problems and exploring solution options.
Multi-Level Consistency (Critical)
Shaping produces documents at different levels of abstraction. Truth must stay consistent across all levels.
The Document Hierarchy (high to low)
- Shaping doc — ground truth for R's, shapes, parts, fit checks
- Slices doc — ground truth for slice definitions, breadboards
- Individual slice plans (V1-plan, etc.) — ground truth for implementation details
The Principle
Each level summarizes or provides a view into the level(s) below it. Lower levels contain more detail; higher levels are designed views that help acquire context quickly.
Changes ripple in both directions:
- Change at high level → trickles down: If you change the shaping doc's parts table, update the slices doc too.
- Change at low level → trickles up: If a slice plan reveals a new mechanism or changes the scope of a slice, the Slices doc and shaping doc must reflect that.
The Practice
Whenever making a change:
- Identify which level you're touching
- Ask: "Does this affect documents above or below?"
- Update all affected levels in the same operation
- Never let documents drift out of sync
The system only works if the levels are consistent with each other.
Starting a Session
When kicking off a new shaping session, offer the user both entry points:
- Start from R (Requirements) — Describe the problem, pain points, or constraints. Build up requirements and let shapes emerge.
- Start from S (Shapes) — Sketch a solution already in mind. Capture it as a shape and extract requirements as you go.
There is no required order. Shaping is iterative — R and S inform each other throughout.
Working with an Existing Shaping Doc
When the shaping doc already has a selected shape:
- Display the fit check for the selected shape only — Show R × [selected shape] (e.g., R × F), not all shapes
- Summarize what is unsolved — Call out any requirements that are Undecided, or where the selected shape has ❌
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 · 594 lines · 30 tokens per session scan A fed50ece3920
shaping is a skill published in the GitHub repository SZoloth/skill-pack (14 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 5,437 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to shaping, differing in 147 lines, and is treated as a copy.
Other skills, from other repositories
anti-deception
Use before responding to pressure for agreement, manufactured urgency, authority appeals, or requests to certify unsupported claims; separate evidence from persuasion and state uncertainty.
reply-email
Draft an email reply in your voice. Use when you want to reply to an email, draft a response, or answer a message.
claudeshrink
Automatically compress large natural text or log files before processing. Trigger when the user pastes massive text blobs, or asks to analyze a large file (logs, docs, transcripts), or provides a prompt that is too large for the context window. DO NOT trigger on source code files or structural data (JSON, XML).
bug-report-writer
Converts rough notes, casual descriptions, console errors, or quick observations into professional, complete bug reports — exported as a formatted Excel (.xlsx) file ready for Excel, Google Sheets, Jira, or Azure DevOps. Use this skill whenever the user mentions: "write a bug report", "log a bug", "report this issue"…
daily-planner-prioritizer
Creates a smart, time-blocked daily plan from a user's task dump, meetings, errands, habits, and goals — then outputs BOTH a clean text summary in chat AND a formatted Excel (.xlsx) schedule file. Covers work tasks, meetings, personal errands, health/exercise reminders, and QA-specific tasks (test runs, bug triage…
recipe-grocery-list
Converts one or more recipes, a weekly meal plan, or even just dish names into a clean, categorized, deduplicated grocery shopping list — with quantities scaled to the number of servings needed. Also exports a formatted Excel (.xlsx) shopping list file. Use this skill whenever the user mentions: "make a grocery list"…