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 fxd0h/Axelera-Voyager-Local-Assistant --skill voyager-testgit clone --depth 1 https://github.com/fxd0h/Axelera-Voyager-Local-AssistantWrote 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/fxd0h/axelera-voyager-local-assistant/voyager-test)<a href="https://agentmods.dev/skills/fxd0h/axelera-voyager-local-assistant/voyager-test"><img src="https://agentmods.dev/badge/skills/fxd0h/axelera-voyager-local-assistant/voyager-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/fxd0h/axelera-voyager-local-assistant/voyager-test"><img src="https://agentmods.dev/badge/skills/fxd0h/axelera-voyager-local-assistant/voyager-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.00051 | $0.01559 |
| Opus 5 | $0.00026 | $0.00779 |
| Sonnet 5 | $0.00010 | $0.00312 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade A, and why
voyager-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 12d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests
Execute tests for Voyager SDK components targeting Axelera AI hardware
Instructions
Run tests based on the specified scope: $ARGUMENTS
{{INCLUDE common/voyager-sdk-setup.md}}
{{INCLUDE common/voyager-task-integration.md}}
Step 1: Environment Setup
- Read
.voyager-runtime.jsonbefore choosing tests:package_for_linux: run host-safe static/unit checks only and report that hardware/runtime tests were not executed.execute_on_device: hardware/runtime tests may run when the SDK and device are visible.
- The setup include (Step 0/Step 3) activates the SDK environment
(
venv/oraxelera-env/); verify withpython -c "import axelera". - Test configuration lives in the SDK's
pyproject.tomlunder[tool.pytest.ini_options](testpaths:tests,internal_tools_tests,run_tests.py). Plainpytestfrom the SDK root uses those paths. - Install optional pytest plugins (
pytest-cov,pytest-xdist,pytest-html,pytest-random-order) only when the user approves environment mutation.
Step 2: Test Scope Identification
Parse test scope from arguments:
all: Run all testsunit: Run unit tests onlyruntime: Run runtime-specific tests<module>: Run tests for specific module<file>: Run specific test file<pattern>: Run tests matching pattern
Step 3: Running Tests with Pytest
This is the canonical flow; the SDK has no tox configuration.
# Run all tests
pytest tests/
# Run specific test file
pytest tests/test_axelera_config.py
# Run specific test function
pytest tests/test_axelera_config.py::test_function_name
# Run tests matching pattern
pytest tests/ -k "config"
pytest tests/ -k "network and not slow"
# Run with verbose output
pytest tests/ -v
# Run with very verbose output (show locals)
pytest tests/ -vv
Step 4: Coverage Reports
# Run with coverage
pytest tests/ --cov=. --cov-report=html --cov-report=term
# View HTML coverage report
xdg-open htmlcov/index.html
# Coverage for specific module
pytest tests/ --cov=axelera/app --cov-report=term-missing
What ships with it
6 files 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.
- 12d ago First seen · 255 lines · 51 tokens per session scan A 15ee62c2cc1b
voyager-test is a skill published in the GitHub repository fxd0h/Axelera-Voyager-Local-Assistant (4 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,559 once invoked, about $0.0003 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
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
junit-5-skill
Generates production-grade JUnit 5 unit and integration tests in Java. Covers assertions, parameterized tests, lifecycle hooks, mocking with Mockito, and nested tests. Use when user mentions "JUnit", "JUnit 5", "@Test", "assertEquals", "Assertions", "Java unit test". Triggers on: "JUnit", "@Test", "assertEquals"…
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.