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-library-verificationgit clone --depth 1 https://github.com/dev-lou/PixelPilotWhat 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.01806 | $0.01806 |
| Opus 5 | $0.00903 | $0.00903 |
| Sonnet 5 | $0.00361 | $0.00361 |
| Haiku 4.5 | $0.00181 | $0.00181 |
Grade A, and why
PixelPilot uiux-library-verification.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 2d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Library Verification Skill
Before recommending any third-party library, AI must verify its health and suitability.
VERIFICATION CHECKLIST
Rule: Never recommend a library without completing this verification. Output results in a standardized table.
Required Checks
| Check | Criteria | Action if Failed |
|---|---|---|
| Exists | Package found on npm or GitHub | Do not recommend |
| Last Update | ≤ 12 months ago | Warn user, suggest alternatives |
| Downloads | ≥ 10,000/week (popular) or ≥ 1,000/week (niche) | Warn user |
| License | MIT, Apache 2.0, BSD, ISC, or MIT-compatible | Do not recommend without explicit user consent |
| Bundle Size | Reasonable for category | Note in recommendation |
| TypeScript | Has types (built-in or @types/*) | Note if missing |
OUTPUT FORMAT
Always output verification results in this table format:
### Library Verification Report
| Library | Exists? | Weekly Downloads | Last Update | License | Bundle Size | Recommendation |
|---------|---------|------------------|-------------|---------|-------------|----------------|
| fuse.js | ✅ Yes | 1.2M | 2 months ago | Apache-2.0 | 24KB | ✅ Recommended |
| some-lib | ✅ Yes | 500 | 18 months ago | MIT | 8KB | ⚠️ Low activity |
| fake-lib | ❌ No | N/A | N/A | N/A | N/A | ❌ Does not exist |
VERIFICATION PROCESS
Step 1: Check npm Registry
// Verification script (run via Node.js or use npm API)
async function verifyPackage(packageName) {
const response = await fetch(`https://registry.npmjs.org/${packageName}`);
if (!response.ok) {
return { exists: false, reason: 'Package not found on npm' };
}
const data = await response.json();
const latest = data['dist-tags']?.latest;
const latestVersion = data.versions?.[latest];
return {
exists: true,
name: data.name,
version: latest,
license: latestVersion?.license || 'Unknown',
lastPublish: data.time?.[latest],
repository: latestVersion?.repository?.url,
types: latestVersion?.types || latestVersion?.typings ||
data.name.startsWith('@types/') ||
!!latestVersion?.devDependencies?.['@types/' + data.name]
};
}
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.
- 2d ago First seen · 252 lines · 1,806 tokens per session scan A aa87febea607
PixelPilot uiux-library-verification.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,806 tokens to every session, about $0.0090 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-08-31.
Other instructions, from other repositories
arai CLAUDE.md
Instructions for taniwhaai/arai, covering claude.md — arai, commands, architecture, prompt-collector module (src/promptcollector.rs) and extending the match pipeline.
healthcare-agents AGENTS.md
Instructions for ajhcs/healthcare-agents, covering healthcare agents repository instructions, repository map, git workflow and self-improvement loop.
arai AGENTS.md
Instructions for taniwhaai/arai, covering agents.md — arai, core discipline (non-negotiable), taniwha / subagent rules, work style and tool usage.
shenzjd-skills CLAUDE.md
Claude Code instructions for wu529778790/shenzjd-skills, covering claude.md, project overview, commands, a single skill's unit test and architecture.
ui-ux-design-pro-skill CLAUDE.md
Instructions for saifyxpro/ui-ux-design-pro-skill, covering project overview, cli commands, full design system generation (markdown output), search across all databases (sub-50ms) and audit ui code quality.
syncai copilot-instructions.md
Instructions for dmtrkzntsv/syncai, covering claude.md, build & run, architecture, lifecycle and identify is the routing decision.