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 painhardcore/pstack --skill principle-redesign-from-first-principlesgit clone --depth 1 https://github.com/painhardcore/pstackWrote 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/painhardcore/pstack/principle-redesign-from-first-principles)<a href="https://agentmods.dev/skills/painhardcore/pstack/principle-redesign-from-first-principles"><img src="https://agentmods.dev/badge/skills/painhardcore/pstack/principle-redesign-from-first-principles/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/painhardcore/pstack/principle-redesign-from-first-principles"><img src="https://agentmods.dev/badge/skills/painhardcore/pstack/principle-redesign-from-first-principles.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.00043 | $0.00181 |
| Opus 5.5 | $0.00017 | $0.00072 |
| Sonnet 5.5 | $0.00009 | $0.00036 |
| Haiku 4.5 | $0.00004 | $0.00018 |
Grade A, and why
principle-redesign-from-first-principles 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
91% identical to principle-redesign-from-first-principles — 9 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.
What it actually says
Redesign From First Principles
When integrating a change, don't bolt it onto the existing design. Redesign as if the requirement had been there from the start. The result should look like what we would have built if we'd known on day one.
- Read all affected files and understand the current design holistically
- Ask: "if we were writing this from scratch with this new requirement, what would we build?"
- Propagate the change through every reference: types, docs, examples, rationale sections
- Think about the redesign holistically, then deliver it incrementally
This is the method for preserving option value when integrating changes into an existing design.
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 · 16 lines · 43 tokens per session scan A bd51e67f78ee
principle-redesign-from-first-principles is a skill published in the GitHub repository painhardcore/pstack (12 stars, last pushed 8d ago), licensed MIT. It adds 43 tokens to every session and 181 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to principle-redesign-from-first-principles, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
creating-figures
Creates publication-quality scientific figures for academic papers. Backend is chosen by host paper extension — .tex papers get TikZ figures, .typ papers get CeTZ figures; the two are never mixed. Use when creating block diagrams, system architectures, flowcharts, or technical illustrations for papers and theses.…
ui
Opinionated constraints for building better web interfaces with coding agents. Use this skill whenever the user asks you to build, review, or fix a UI — landing pages, dashboards, components, or any frontend code — and whenever you write Tailwind CSS, motion/react animations, accessible component primitives (Base UI…
logo-designer
Design and iterate on logos using SVG. Use this skill when the user asks to "create a logo", "design a logo", "make me a logo", "iterate on this logo", "logo for my project", or discusses logo design, branding icons, or wordmarks.
wp-patterns
A workflow for creating and updating WordPress block patterns, which are reusable layouts made from the block editor's content blocks. It also reviews their registration, accessibility, translations, and safe use of theme design settings.
ui-first-principles
A method for deciding which information and actions should appear first in a user interface or information architecture.
form-patterns
A Russian-language reference for designing managed 1C forms. It describes layout patterns, common conventions, user-experience rules, form archetypes, and advanced techniques.