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 skills add nWave-ai/nWave --skill nw-fp-usable-designgit clone --depth 1 https://github.com/nWave-ai/nWaveWrote 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/nwave-ai/nwave/nw-fp-usable-design)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-fp-usable-design"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-fp-usable-design/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/nwave-ai/nwave/nw-fp-usable-design"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-fp-usable-design.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.00020 | $0.02003 |
| Opus 5 | $0.00010 | $0.01001 |
| Sonnet 5 | $0.00004 | $0.00401 |
| Haiku 4.5 | $0.00002 | $0.00200 |
Grade A, and why
nw-fp-usable-design 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 5d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FP Usable Design
Make functional code usable. The developer is the user of your design. Apply usability thinking to code organization, naming, and architecture.
Cross-references: fp-domain-modeling | fp-hexagonal-architecture | fp-algebra-driven-design
1. Core Insight
[STARTER]
The user of software design is the developer, not the end user. When developers struggle, blame the design, not the people. Pressure, team churn, unclear specs, and noisy environments produce unusable designs. Improve the design.
2. Five Evaluation Goals
[STARTER]
| Goal | What It Means | How to Assess |
|---|---|---|
| Learnability | How quickly a new developer becomes productive | Timed tasks for unfamiliar developers |
| Efficiency | How fast common tasks are performed | Count unnecessary navigation and decisions |
| Memorability | How easily proficiency returns after time away | What do returning developers re-learn? |
| Error resistance | How many bugs the design induces | Track bug locations; ask "what design change prevents this category?" |
| Satisfaction | How pleasant to work in the codebase | Developer interviews, retrospectives |
3. Naming Conventions
[STARTER]
Domain Language in Function Names
Use domain expert's vocabulary, not mathematical conventions or technical jargon. No OrderFactory, OrderManager, OrderHelper.
Verb-Noun for Transformations (Pipeline-Friendly)
rawOrder
|> validateOrderFields
|> enrichWithCustomerData
|> calculateOrderTotal
|> applyDiscountRules
|> generateOrderConfirmation
Predicate Functions Use Question-Style Names
isActiveCustomer -- not: checkActive, activeP
hasShippingAddress -- not: shippingAddr, addrCheck
canPlaceOrder -- not: orderOk, validateOrderBool
When Short Names Are Acceptable
Single-letter names appropriate only in: library internals and generic utilities | lambda parameters in trivial operations | type variables | mathematical domains where convention IS domain language.
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.
- 5d ago First seen · 238 lines · 20 tokens per session scan A 4b3aba348ff8
nw-fp-usable-design is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 2,003 once invoked, about $0.0001 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 skills, from other repositories
sage-review
Deep, platform-neutral code review for PRs and CRs in ONE thorough single pass — design reasoning (Problem Worth Solving & Solution Fit) as one dimension alongside the 9 code-level dimensions, with chain-of-consequences, self-critique, and draft-only comments. The single app-owned source of truth.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
demand-elegance
Challenges hacky fixes on non-trivial changes.
design-review
Use when the user wants to evaluate something that ALREADY EXISTS rather than build something new — "review this", "audit this screen", "what's wrong with this page", "is this accessible?", or when they share a screenshot, URL, or existing code/markup. Runs the existing reviewers (design-critic…
team-implement
Executes and verifies implementation slices. Trigger on "implement this", "execute the plan", or "/team-implement" only; never infer the phase from a ready plan.
prune
Run all quality lenses (validate, simplify), aggregate findings into a design doc, then drive the full feature chain (PRD → TDD → PR) to fix them systematically.