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 BackToCimaCoppi/Praxis --skill site-previewgit clone --depth 1 https://github.com/BackToCimaCoppi/PraxisWrote 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/backtocimacoppi/praxis/site-preview)<a href="https://agentmods.dev/skills/backtocimacoppi/praxis/site-preview"><img src="https://agentmods.dev/badge/skills/backtocimacoppi/praxis/site-preview/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/backtocimacoppi/praxis/site-preview"><img src="https://agentmods.dev/badge/skills/backtocimacoppi/praxis/site-preview.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.00071 | $0.00672 |
| Opus 5.5 | $0.00028 | $0.00269 |
| Sonnet 5.5 | $0.00014 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
site-preview 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 29d 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
手机审阅站
本地原件是内容真值；审阅站是可更新的临时展示副本，不取得设计或业务裁决权。
准备材料
- 确定输入材料及本地原件。HTML 保留视觉与必要依赖；Markdown 完整转换成手机可读的 HTML，不摘要或改变结论。
- 在隔离 staging 目录中只放
index.html和实际需要的本地 CSS、JS、图片、字体。缺少依赖时停止；禁止复制整个项目、凭据、.env、Git 元数据、数据库、日志或会话文件。 - 使用本 skill 的
scripts/site_preview.py管理本地目录。init建站，upsert新增或更新，list查询，remove移除单项，clear清空材料，lock保护并发写入；具体参数由--help查询。路径、站名和项目标识由使用者或项目配置提供，不写死在 skill 中。 - 目录按项目、任务、材料三级 slug 组织；同一材料更新复用原 slug，保持目录和已发布直链稳定。本地 HTTP 打开首页与材料页，在手机宽度下检查可读性和依赖。
可选发布
- 只有当前环境存在已配置的托管能力、目标站点与访问策略可核实，且本次发布已获授权，才将本地目录发布。优先沿用项目明确指定的私有托管流程；有 Sites 能力时可调用其正式 building/hosting skill。不得自动创建公开站、扩大访问者或把临时令牌当交付链接。
- 发布前持有
lock；确认远端当前版本，避免用旧目录覆盖他人材料。构建、保存和部署成功后核验首页、材料直链与访问范围，再释放锁。失败时保留最后成功版本并报告阻塞，不声称发布成功。 - 未配置托管、当前模式禁止联网/部署或用户要求仅本地时，交付本地预览与目录路径，并明确“未发布”；不得将缺少托管视为材料制作失败。
remove只移除指定材料；clear仅在用户明确要求清空全部预览时执行。两者均不删除本地原件，不承诺清除托管平台历史版本。
交付
报告材料名称和本地位置；已发布时附材料直链、首页和访问范围。设计预览的截图自检仍由 design-preview 完成；审阅意见由调用方写回正式文档。
What ships with it
2 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.
- 29d ago First seen · 27 lines · 71 tokens per session scan A 70e926bf8725
site-preview is a skill published in the GitHub repository BackToCimaCoppi/Praxis (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 672 once invoked, about $0.0003 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-09-24.
Other skills, from other repositories
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…
figma-design-handoff
Figma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev…
animation-motion-design
Animation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.
component-search
Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system…
web-artifacts
Turns any idea into a live single-file HTML prototype in minutes — inline CSS/JS, CDN-only dependencies (cdnjs), mobile-first, seeded with believable fake data, interactive states wired — ready to open in a browser or paste as a Claude artifact. Use when the user says "prototype this", "show me a working demo", "make…
light-dark-mode
Load this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level…