Borrowing it
Nothing to install: this file belongs to act-sdk/act-sdk-js. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/act-sdk/act-sdk-js/main/.agents/skills/square-corners/SKILL.mdgit clone --depth 1 https://github.com/act-sdk/act-sdk-jsWrote 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/act-sdk/act-sdk-js/square-corners)<a href="https://agentmods.dev/skills/act-sdk/act-sdk-js/square-corners"><img src="https://agentmods.dev/badge/skills/act-sdk/act-sdk-js/square-corners/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/act-sdk/act-sdk-js/square-corners"><img src="https://agentmods.dev/badge/skills/act-sdk/act-sdk-js/square-corners.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.00036 | $0.00370 |
| Opus 5.5 | $0.00014 | $0.00148 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
square-corners 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.
What it actually says
Apply this skill when building or restyling PlanWiki UI.
Core rule
- Default shared primitives in
components/uitorounded-sm. - Default composed PlanWiki surfaces outside
components/uitorounded-sm. - Treat
rounded-smas the project style for workspace pages, widgets, cards, badges, chips, stats, tables, controls, and overlays that make up the product UI. - Do not introduce
rounded-none,rounded-md,rounded-lg,rounded-xl, or pill-shaped treatments unless the user explicitly requests them.
What to preserve
- Keep the existing flat, minimal visual language.
- Prefer borders and spacing over decorative shape styling.
- Keep circular affordances that rely on
rounded-fullfor their function or iconography. - If a component comes from a shared UI primitive with
rounded-smdefaults, preserve that shape at usage sites unless the user asks otherwise.
When working on existing files
- Remove accidental corner overrides that flatten or over-round feature surfaces.
- Check usage sites, not just base components. A feature can still drift away from the default through local class overrides.
- Keep sidebar behavior and established layout patterns intact unless the user asks for structural changes.
Quick checklist
components/ui:rounded-smby default- Cards:
rounded-sm - Widget shells:
rounded-sm - Badges/chips/status pills:
rounded-sm - Buttons in workspace UI:
rounded-sm - Inputs, textareas, tables, dropdown surfaces:
rounded-sm
If there is any ambiguity, use rounded-sm.
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 · 38 lines · 36 tokens per session scan A fde5353fa4e2
square-corners is a skill published in the GitHub repository act-sdk/act-sdk-js (3 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 370 once invoked, about $0.0001 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
web-visuals
Make images, textures, illustrations and background video for a website or app you are building, with Glif, and wire them into the code. Use when: "add a hero image", "this page needs visuals", "replace these stock photos", "placeholder images", "background texture", "seamless pattern", "paper grain", "section…
Aesthetic Web Design
Apply professional, premium UI/UX design standards when building or styling web interfaces. Use this skill when the user asks to create a website, landing page, web app, dashboard, UI component, or any visual interface — or when they ask to make something look better, more professional, or more beautiful. Covers…
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers design systems, anti-pattern detection, brand vs product registers, typography, color (OKLCH), spacing, motion, copy, and…
taste-soft
High-end visual design like a premium agency. Defines exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks common defaults that make AI designs look cheap or generic. Based on taste-skill by Leon Lin & blueemi, improved by shokunin.
shadcn-sveltekit-design
Use when building, redesigning, beautifying, or refactoring SvelteKit pages and reusable components with shadcn-svelte, Bits UI, or the shadcn-svelte MCP. Trigger on landing pages, dashboards, marketing sites, app shells, forms, navbars, tables, dialogs, charts, sidebars, auth screens, blocks, responsive layouts…
html-design-revision
Revise an existing HTML/CSS design file with small, safe edits. Use when asked to change a color, text, size, position or add an element to a design that already exists. Use other tools for building a design from scratch.