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 skills/lenxism/ives/quality-facetsnpx skills add lenxism/ives --skill quality-facetsgit clone --depth 1 https://github.com/lenxism/ivesWrote 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/lenxism/ives/quality-facets)<a href="https://agentmods.dev/skills/lenxism/ives/quality-facets"><img src="https://agentmods.dev/badge/skills/lenxism/ives/quality-facets.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.00099 | $0.00700 |
| Opus 5 | $0.00049 | $0.00350 |
| Sonnet 5 | $0.00020 | $0.00140 |
| Haiku 4.5 | $0.00010 | $0.00070 |
Grade A, and why
quality-facets 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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Facets
How do you know what you're designing is good — not just functional, but good in the way you want it to be perceived? Facets are the answer.
Defining Your Facets
Facets are external characteristics you want users to perceive — what they see, experience, and feel. They are NOT generic qualities all products should have (like "useful" or "reliable"). They're specific and situational.
How to define them
Ask: "When someone uses this, what do I want them to feel and perceive?"
Each facet should be:
- Specific to your product — not universal
- Externally perceivable — something users experience
- Distinct from others — each captures something different
- Aspirational — what you're striving for
Examples
Design education platform: Crafted, Fidgetable, Authentic, Expansive, Inventive
Legal/financial app: Trustworthy, Calm, Expert, Supportive
Developer tool: Fast, Precise, Extensible, Native
Your list will be different. That's the point.
Evaluating (1-5 Scale)
- 1 — Absolute minimum you can live with
- 3 — Meets expectations, solid but unremarkable
- 5 — Best you can imagine
Rate each facet honestly. This often reveals surprises:
- Your strongest facet might be something you weren't focused on
- Your weakest might be what users care about most
- You might be over-investing in one area at another's expense
Using Facets
For planning
Lowest-rated facets that matter most should drive your roadmap.
For critique
Instead of "this doesn't feel right":
"This doesn't feel inventive enough. We were at 4, this feels like we're going backwards."
For team alignment
Shared vocabulary for productive tradeoff conversations:
"This feature improves Expansive from 1.5 to 2.5, but brings Crafted down from 3 to 2.5. Right tradeoff?"
For tracking
Measure at each release. Prevents quality regression — catch it before users feel it.
Constants vs. Facets
Some qualities are constants — true of ALL good products: consistent, well-built, accessible, performant. These aren't facets — they're table stakes.
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.
- 4d ago First seen · 81 lines · 99 tokens per session scan A 07c90bcf941d
quality-facets is a skill published in the GitHub repository lenxism/ives (5 stars, last pushed 6mo ago), licensed MIT. It adds 99 tokens to every session and 700 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…