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 archestra-ai/archestra --skill archestra-dev-testinggit clone --depth 1 https://github.com/archestra-ai/archestraWrote 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/archestra-ai/archestra/archestra-dev-testing)<a href="https://agentmods.dev/skills/archestra-ai/archestra/archestra-dev-testing"><img src="https://agentmods.dev/badge/skills/archestra-ai/archestra/archestra-dev-testing/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/archestra-ai/archestra/archestra-dev-testing"><img src="https://agentmods.dev/badge/skills/archestra-ai/archestra/archestra-dev-testing.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.00038 | $0.02938 |
| Opus 5.5 | $0.00015 | $0.01175 |
| Sonnet 5.5 | $0.00008 | $0.00588 |
| Haiku 4.5 | $0.00004 | $0.00294 |
Grade A, and why
archestra-dev-testing 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 18d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 18d ago Changed abcedea6955e
- 25d ago Changed · +38 lines · -30 tokens per session 6a4712f346ab
- 1mo ago Changed · +2 lines 9de8f2aac4c8
- 1mo ago First seen · 244 lines · 68 tokens per session scan A fb54b834488c
archestra-dev-testing is a skill published in the GitHub repository archestra-ai/archestra (4,380 stars, last pushed today), with no licence file. It adds 38 tokens to every session and 2,938 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
harn-testing
Test owning interfaces, canonical paths, liveness, replay, and stochastic quality at the right altitude.
medusa-testing
Test Medusa v2 applications — Jest setup, module unit tests, workflow integration tests, API route tests, medusaIntegrationTestRunner, and mock patterns. Use when writing tests for Medusa projects.
sf-testing
Test Salesforce Commerce code — B2C (Node.js unit testing, sfcc-ci CI/CD, sandbox management, linting) and B2B (Apex test classes with 75% coverage minimum, Jest for LWC, sf CLI deployment and validation). Use when writing tests or setting up CI/CD.
saleor-testing
Test Saleor applications — pytest setup, Django test client, GraphQL test patterns, App testing, factoryboy fixtures, and webhook testing. Use when writing tests for Saleor projects.
a2a-testing
Test A2A implementations — unit tests, integration tests, mock agents, protocol conformance, and end-to-end multi-agent testing. Use when building test suites for A2A servers, clients, or multi-agent systems.
magento-testing
Write tests for Magento 2 — PHPUnit unit tests, integration tests, MFTF functional tests, and API tests. Use when implementing test coverage for modules, debugging, or setting up CI/CD test pipelines.