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 AI-Unified-Process/marketplace --skill hilla-ui-testgit clone --depth 1 https://github.com/AI-Unified-Process/marketplaceWrote 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/ai-unified-process/marketplace/hilla-ui-test)<a href="https://agentmods.dev/skills/ai-unified-process/marketplace/hilla-ui-test"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/hilla-ui-test/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/ai-unified-process/marketplace/hilla-ui-test"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/hilla-ui-test.svg" alt="Reviewed on agentmods" width="80" 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.00224 | $0.00608 |
| Opus 5.5 | $0.00090 | $0.00243 |
| Sonnet 5.5 | $0.00045 | $0.00122 |
| Haiku 4.5 | $0.00022 | $0.00061 |
Grade A, and why
hilla-ui-test 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 today.
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.
What it actually says
Hilla UI Test
Instructions
Write the UI layer tests of the use case $ARGUMENTS for the Hilla view with Vitest in browser mode and React Testing
Library, the generated endpoint clients mocked with vi.spyOn — no server, no database. Each suite is
src/main/frontend/tests/UC-XXX-<slug>.test.tsx with describe('UC-XXX: <name>').
Run Directly or from /use-case-test
Run from /use-case-test, this skill follows that skill's sections "If Tests for This Use Case Already Exist",
"When a Test Fails", and "Which Layer Tests What"; it does not repeat them. The specification is the oracle: take
every expected value from it, never from what the code returns.
What to Test
What the actor sees: rendering, form validation, the call the view makes, and the message the specification states
for each outcome and alternative flow. The business rules are tested by the integration layer's test skill. Also
write one Java test of the endpoint, UC<id><Name>EndpointTest: its access annotation and the EndpointException
message of each alternative flow.
Markers
Keep this skill's rows in the Markers table of docs/architecture/stack.md exactly as
references/markers.md lists them: add them when they are missing, correct them when they
differ. Touch no other row.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 47 lines · 224 tokens per session scan A 7b6d20df13c0
hilla-ui-test is a skill published in the GitHub repository AI-Unified-Process/marketplace (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 224 tokens to every session and 608 once invoked, about $0.0009 per session on Opus 5.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-10-25.
Other skills, from other repositories
react-native-testing
Write tests using React Native Testing Library (RNTL) v13 and v14 (@testing-library/react-native). Use when writing, reviewing, or fixing React Native component tests. Covers: render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns. Supports v13 (React…
vitest
Set up Vitest testing in any project — detects type (Cloudflare Workers, React, Node, library), generates vitest.config.ts, test setup, utilities, and a sample test. Covers mocking patterns, coverage config, workspace setup, Jest migration. Use whenever the user mentions adding tests, setting up Vitest, configuring…
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
authoring-data-quality-checks
Adds and runs data quality checks (dbt-test style assertions) on a project's warehouse tables and saved-query views, and HogQL catalog metrics: not-null, uniqueness, accepted values, referential integrity, row-count bounds, freshness, and custom HogQL. Metrics support custom SQL checks only. Use when asked to test a…
appbuilder-testing
Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib- clients, ExC…
angular-testing
Write Angular component tests using TestBed, ComponentHarness, and HttpTestingController with proper signal input handling. Use when writing component tests, mocking HTTP calls, or testing signal inputs.