Instatic is a self-hosted content management system with a visual editor, content tools, and publishing in one Bun server, producing static HTML and CSS pages. It is used to build and manage websites such as blogs, portfolios, and small-business sites.
Borrowing it
Nothing to install: this file belongs to CoreBunch/Instatic. 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/CoreBunch/Instatic/main/.agents/skills/instatic-user-e2e/SKILL.mdgit clone --depth 1 https://github.com/CoreBunch/InstaticWrote 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/corebunch/instatic/instatic-user-e2e)<a href="https://agentmods.dev/skills/corebunch/instatic/instatic-user-e2e"><img src="https://agentmods.dev/badge/skills/corebunch/instatic/instatic-user-e2e/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/corebunch/instatic/instatic-user-e2e"><img src="https://agentmods.dev/badge/skills/corebunch/instatic/instatic-user-e2e.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00083 | $0.01099 |
| Opus 5.5 | $0.00033 | $0.00440 |
| Sonnet 5.5 | $0.00017 | $0.00220 |
| Haiku 4.5 | $0.00008 | $0.00110 |
Grade A, and why
instatic-user-e2e 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instatic User E2E
Overview
Use this skill to operate Instatic like a real user through the browser, record product-quality findings, and keep durable run logs. This is not a replacement for bun test; it covers the gaps that unit, API, architecture, and happy-dom tests cannot see.
Core Rule
Treat browser-observed behavior as primary evidence. Use code, database, API, or localStorage inspection only to reset the environment, unblock the run, or triage an issue already observed through the UI.
Required References
- Read
docs/e2e/protocol.mdbefore running or changing the protocol. - Read
docs/e2e/feature-matrix.mdbefore choosing scenarios. - Use
docs/e2e/run-log-template.mdwhen writing a new run log. - Use the project-local
agent-browserskill or the available in-app Browser tooling for browser control.
Default Scope
If the user does not name a scope, run the Core Owner Lifecycle:
- Fresh install setup.
- Owner login/logout.
- Open the editor.
- Create or edit a page.
- Add and style basic content.
- Save/reload persistence check.
- Publish.
- Visit the public page as a non-admin user.
Environment Setup
Prefer an isolated SQLite database and upload directory for each run:
DATABASE_URL=sqlite:./.tmp/e2e-agent.db \
UPLOADS_DIR=./.tmp/e2e-uploads \
bun run dev
Before deleting data, verify the target is disposable:
- Safe:
.tmp/e2e-*,.tmp/dev.db, temporary uploads under.tmp/. - Unsafe without explicit user instruction: production-looking Postgres URLs, non-temporary upload directories, checked-in fixtures.
If ports are busy, inspect them and avoid killing processes you did not start unless the user explicitly gave control of the running app. When possible, use the already-running local app and log the DB/reset limitation.
Run Workflow
- Record repo state: current branch, HEAD SHA, and whether the worktree is dirty.
- Select scenario rows from
docs/e2e/feature-matrix.md. - Reset only disposable data for the run.
- Start or identify the local app URL, usually
http://localhost:5173/admin. - Use the browser as a user. Prefer visible labels and accessible names over test IDs or internal selectors.
- Capture screenshots at the required proof points in
docs/e2e/protocol.md, plus any time a visual issue or confusing state appears. - Log every scenario result in
docs/e2e/runs/YYYY-MM-DD-<scope>.md. - File issues inside the run log before investigating implementation details.
- Summarize blockers, top issues, and recommended next fixes.
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 · 130 lines · 83 tokens per session scan A 3397bf7f04e4
instatic-user-e2e is a skill published in the GitHub repository CoreBunch/Instatic (8,966 stars, last pushed 4d ago), licensed MIT. It adds 83 tokens to every session and 1,099 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-08-30.
Other skills, from other repositories
ux-acceptance-tester
Perform a goal-driven, black-box UX acceptance journey in a browser and report the path, friction, and observable outcome. Use only in an isolated tester context with a supplied start URL and brief.
ux-acceptance-coordinator
Coordinate black-box, agent-driven UX acceptance journeys against a disposable EmDash admin site. Use when preparing, dispatching, verifying, or reporting a manual browser journey performed by a separate tester agent. Do not use for deterministic Playwright tests or ordinary code review.
test-component
Runs, analyzes, and fixes cross-framework interaction, visual-snapshot, aria-snapshot, and accessibility tests for a specific DB UX component's showcase pages.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, measures every call (bytes, token estimate, wall-clock) and weighs the catalog, renders app tools' views in a headless MCP Apps host, and produces a…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.