Borrowing it
Nothing to install: this file belongs to RedHatInsights/nxtcm-components. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RedHatInsights/nxtcm-components/main/.agents/skills/stryker-mutation-test/SKILL.mdgit clone --depth 1 https://github.com/RedHatInsights/nxtcm-componentsWrote 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/redhatinsights/nxtcm-components/stryker-mutation-test)<a href="https://agentmods.dev/skills/redhatinsights/nxtcm-components/stryker-mutation-test"><img src="https://agentmods.dev/badge/skills/redhatinsights/nxtcm-components/stryker-mutation-test.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.1 | $0.00076 | $0.01224 |
| Opus 5 | $0.00038 | $0.00612 |
| Sonnet 5 | $0.00015 | $0.00245 |
| Haiku 4.5 | $0.00008 | $0.00122 |
Grade A, and why
stryker-mutation-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 7d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stryker mutation test command builder
Construct the correct npm run test:stryker command from what the user says. Never run it (no Shell, no npm run test:stryker). Give the user a copy-paste command and ask them to run it locally.
Workflow
- Parse the request — which component(s) or test file(s) did they mean?
- Resolve paths — map names to repo-relative
*.tsxcomponent files (not specs). - Add flags —
--report,STRYKER_CONCURRENCYwhen appropriate. - Output — one fenced
bashblock + short notes (runtime, prerequisites). - Ask the user to run the command in their terminal and paste results if they want help interpreting them.
Command shape
npm run test:stryker -- [stryker-target flags] <component.tsx> [more-components.tsx ...]
With HTML report:
npm run test:stryker:report -- <component.tsx> [more...]
# same as: npm run test:stryker -- --report <component.tsx> ...
Optional env prefix (parallel workers, default is min(4, max(1, cpuCount - 1))):
STRYKER_CONCURRENCY=2 npm run test:stryker -- <component.tsx>
Resolving what to mutate
Pass the component .tsx file, never the .spec.tsx.
| User says | Resolve to |
|---|---|
FieldWithAPIErrorAlert |
packages/nxtcm-rosa-hcp-wizard/src/components/FieldWithAPIErrorAlert.tsx |
FieldWithAPIErrorAlert.spec.tsx |
Same component path (strip .spec) |
rosa hcp footer / RosaHcpWizardFooter |
packages/nxtcm-rosa-hcp-wizard/src/Footer/RosaHcpWizardFooter.tsx |
src/components/Foo (any package) |
packages/<package>/src/components/Foo/Foo.tsx (confirm file exists) |
| Ambiguous basename | Search with Glob; if multiple matches, ask the user to pick |
All paths must be repo-relative from the monorepo root (include the packages/<package>/ prefix when the component lives in a workspace package, not just src/...).
If the user names a spec or you're unsure of the subject, read the .spec.tsx file and trace the mount target and imports to the co-located *.tsx component.
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.
- 7d ago First seen · 121 lines · 76 tokens per session scan A 6c45c525e0cd
stryker-mutation-test is a skill published in the GitHub repository RedHatInsights/nxtcm-components (3 stars, last pushed today), licensed Apache-2.0. It adds 76 tokens to every session and 1,224 once invoked, about $0.0004 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.