Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factorynpx agentmods add skills/jonlwowski012/copilot-agent-factory/run-testsWrote 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/jonlwowski012/copilot-agent-factory/run-tests)<a href="https://agentmods.dev/skills/jonlwowski012/copilot-agent-factory/run-tests"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/run-tests.svg" alt="Measured on agentmods" 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.00015 | $0.01932 |
| Opus 5 | $0.00008 | $0.00966 |
| Sonnet 5 | $0.00003 | $0.00386 |
| Haiku 4.5 | $0.00002 | $0.00193 |
Grade A, and why
run-tests 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 8d 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Run Tests
When to Use This Skill
This skill activates when you need to:
- Run tests in an already-configured project
- Execute tests with specific options (coverage, verbose, specific files)
- Run tests in CI/CD or locally
- Understand test execution commands for this project
Prerequisites
This skill assumes tests are already configured. If not, use the pytest-setup or jest-setup skill first.
Step-by-Step Workflow
Step 1: Detect Test Framework and Command
Check for configured test command:
Look in project configuration files:
package.json→scripts.testpyproject.toml→[tool.pytest]or custom scriptsMakefile→testtarget.github/workflows/→ CI test commandstox.ini→ test commands
If {{test_command}} is defined:
{{test_command}}
Step 2: Run Tests by Tech Stack
Python (pytest)
Basic test run:
pytest
Verbose output:
pytest -v
With coverage:
pytest --cov=src --cov-report=html --cov-report=term
Specific file:
pytest tests/test_example.py
Specific test:
pytest tests/test_example.py::test_function_name
Pattern matching:
pytest -k "test_user" # Run tests matching pattern
Markers:
pytest -m "not slow" # Skip slow tests
pytest -m "integration" # Only integration tests
Parallel execution:
pytest -n auto # Requires pytest-xdist
Stop on first failure:
pytest -x
Show print output:
pytest -s
JavaScript/TypeScript (Jest)
Basic test run:
npm test
# or
yarn test
Watch mode:
npm test -- --watch
Coverage:
npm test -- --coverage
Specific file:
npm test -- tests/example.test.js
Pattern matching:
npm test -- --testNamePattern="user"
Update snapshots:
npm test -- --updateSnapshot
Verbose:
npm test -- --verbose
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.
- 8d ago First seen · 401 lines · 15 tokens per session scan A 4528817ee6ef
run-tests is a skill published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 8d ago), licensed MIT. It adds 15 tokens to every session and 1,932 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-08-30.
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.