Borrowing it
Nothing to install: this file belongs to dev-lou/PixelPilot. 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/dev-lou/PixelPilot/main/vscode/.github/instructions/uiux-seo.instructions.mdgit clone --depth 1 https://github.com/dev-lou/PixelPilotWrote 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/instructions/dev-lou/pixelpilot/uiux-seo)<a href="https://agentmods.dev/instructions/dev-lou/pixelpilot/uiux-seo"><img src="https://agentmods.dev/badge/instructions/dev-lou/pixelpilot/uiux-seo.svg" alt="Measured on agentmods" 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.00948 | $0.00948 |
| Opus 5 | $0.00474 | $0.00474 |
| Sonnet 5 | $0.00190 | $0.00190 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
PixelPilot uiux-seo.instructions.md 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 3d 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.
UI/UX Search Engine Optimization (SEO) 2026
Structured data (JSON-LD), meta tags, sitemap.xml, and robots.txt guidance for static and SSR projects.
1. STRUCTURED DATA (JSON-LD)
Rule: Use JSON-LD for structured data to help search engines understand your content.
<!-- Organization Structured Data -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "OpenCode",
"url": "https://opencode.com",
"logo": "https://opencode.com/logo.png",
"sameAs": [
"https://twitter.com/opencode",
"https://github.com/opencode"
]
}
</script>
<!-- Article Structured Data -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "UI/UX Design Trends 2026",
"image": ["https://opencode.com/images/trends-2026.jpg"],
"datePublished": "2026-04-06T08:00:00+08:00",
"author": {
"@type": "Person",
"name": "Jane Doe"
}
}
</script>
2. META TAGS (Title, Description, OG, Twitter)
<!-- Primary Meta Tags -->
<title>OpenCode — Premium UI/UX Design System 2026</title>
<meta name="title" content="OpenCode — Premium UI/UX Design System 2026">
<meta name="description" content="The definitive UI/UX design system for 2026. Built for performance, accessibility, and luxury.">
<!-- Open Graph / Facebook -->
<meta property="og:type" content="website">
<meta property="og:url" content="https://opencode.com/">
<meta property="og:title" content="OpenCode — Premium UI/UX Design System 2026">
<meta property="og:description" content="The definitive UI/UX design system for 2026. Built for performance, accessibility, and luxury.">
<meta property="og:image" content="https://opencode.com/og-image.jpg">
<!-- Twitter -->
<meta property="twitter:card" content="summary_large_image">
<meta property="twitter:url" content="https://opencode.com/">
<meta property="twitter:title" content="OpenCode — Premium UI/UX Design System 2026">
<meta property="twitter:description" content="The definitive UI/UX design system for 2026. Built for performance, accessibility, and luxury.">
<meta property="twitter:image" content="https://opencode.com/og-image.jpg">
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.
- 3d ago First seen · 130 lines · 948 tokens per session scan A f609031439e6
PixelPilot uiux-seo.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 5mo ago), licensed MIT. It adds 948 tokens to every session, about $0.0047 per session on Opus 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-03.
Other instructions, from other repositories
plugin-files-mode
Rosetta Plugin Mode Bootstrap.
plan-forge landing-zone.instructions.md
Azure Landing Zone baselines — identity, network, policy, management, security, tagging, subscription organization.
plan-forge blazor-fluent-ui.instructions.md
Blazor Server + Microsoft Fluent UI patterns — component layering, state, lifecycle, accessibility. Auto-loads when editing .razor / .razor.cs files.
plan-forge policy.instructions.md
Azure Policy and Initiative compliance — definitions, assignment, compliance state, exemptions, remediation tasks.
plan-forge api-patterns.instructions.md
API patterns for .NET — REST conventions, ProblemDetails, pagination, versioning, error responses.
plan-forge waf.instructions.md
Azure Well-Architected Framework (WAF) guardrails — Reliability, Security, Cost, Operational Excellence, Performance.