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 agentmods add instructions/dev-lou/pixelpilot/uiux-temporal-uigit 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-temporal-ui)<a href="https://agentmods.dev/instructions/dev-lou/pixelpilot/uiux-temporal-ui"><img src="https://agentmods.dev/badge/instructions/dev-lou/pixelpilot/uiux-temporal-ui.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 | $0.04348 | $0.04348 |
| Opus 5 | $0.02174 | $0.02174 |
| Sonnet 5 | $0.00870 | $0.00870 |
| Haiku 4.5 | $0.00435 | $0.00435 |
Grade A, and why
PixelPilot uiux-temporal-ui.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 yesterday.
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 — 628 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Temporal UI — Time-Aware Interfaces
Time matters. A dashboard at 2am should feel different than at 2pm. This file covers time-of-day theming, deadline urgency, personalized greetings, and building interfaces that respect temporal context.
CRITICAL RULES
- User timezone — Always use client-side time, not server time.
- Privacy — Don't log/track user's local time without consent.
- Override option — Let users disable time-based features.
- Graceful transitions — Theme changes should be smooth, not jarring.
- Accessibility — Never rely solely on color for urgency.
TIME-OF-DAY THEME
Automatic theme based on local time:
// temporalTheme.ts
type TimeOfDay = 'night' | 'morning' | 'afternoon' | 'evening';
interface TimeConfig {
night: { start: number; end: number }; // 22:00 - 06:00
morning: { start: number; end: number }; // 06:00 - 12:00
afternoon: { start: number; end: number }; // 12:00 - 18:00
evening: { start: number; end: number }; // 18:00 - 22:00
}
const defaultConfig: TimeConfig = {
night: { start: 22, end: 6 },
morning: { start: 6, end: 12 },
afternoon: { start: 12, end: 18 },
evening: { start: 18, end: 22 },
};
export function getTimeOfDay(config = defaultConfig): TimeOfDay {
const hour = new Date().getHours();
if (hour >= config.night.start || hour < config.night.end) return 'night';
if (hour >= config.morning.start && hour < config.morning.end) return 'morning';
if (hour >= config.afternoon.start && hour < config.afternoon.end) return 'afternoon';
return 'evening';
}
export function applyTemporalTheme(): void {
// Respect manual override
if (localStorage.getItem('theme-manual') === 'true') return;
const timeOfDay = getTimeOfDay();
const systemPrefersDark = window.matchMedia('(prefers-color-scheme: dark)').matches;
// Combine time + system preference
let theme: string;
if (timeOfDay === 'night') {
theme = 'dark';
} else if (timeOfDay === 'evening' && systemPrefersDark) {
theme = 'dark';
} else if (timeOfDay === 'morning') {
theme = 'light-warm'; // Slightly warmer morning light
} else {
theme = 'light';
}
document.documentElement.setAttribute('data-theme', theme);
document.documentElement.setAttribute('data-time-of-day', timeOfDay);
}
// Update every 15 minutes
export function initTemporalTheme(): () => void {
applyTemporalTheme();
const interval = setInterval(applyTemporalTheme, 15 * 60 * 1000);
return () => clearInterval(interval);
}
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.
- yesterday First seen · 628 lines · 4,348 tokens per session scan A 15a50d1ba7ea
PixelPilot uiux-temporal-ui.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 5mo ago), licensed MIT. It adds 4,348 tokens to every session, about $0.0217 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
UIX CLAUDE.md
Instructions for Deepractice/UIX, covering uix project rules, design system: lucid ui, colors, forbidden and preferred patterns.
packmind packmind-front-end-ui-and-design-systems.instructions.md
Instructions for PackmindHub/packmind: This standard establishes guidelines for using Chakra UI v3 through the @packmind/ui design system to ensure consistent UI implementation across the frontend application. The @packmind/ui package prov... .
openbridge-webcomponents ui-components.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering ui components instructions, architecture, elevation variants via @mixin style, slot conventions and event naming.
naksha-studio copilot-instructions.md
Instructions for Adityaraj0421/naksha-studio, covering naksha design team — github copilot, activation triggers, the design team, design rules for code generation and css custom properties (always use these patterns).
lovable-boilerplate design.instructions.md
Instructions for chihebnabil/lovable-boilerplate, covering design system guidelines, critical design rules, never create, always create and core design philosophy.
tidyfactor-design AGENTS.md
Instructions for alwkala/tidyfactor-design, covering ⚡ skill & 24 modular slash commands (7 lifecycle stages) and critical architecture (non-negotiable).