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 ExcaliburOSS/excalibur-core --skill testinggit clone --depth 1 https://github.com/ExcaliburOSS/excalibur-coreWrote 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/excalibuross/excalibur-core/testing)<a href="https://agentmods.dev/skills/excalibuross/excalibur-core/testing"><img src="https://agentmods.dev/badge/skills/excalibuross/excalibur-core/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/excalibuross/excalibur-core/testing"><img src="https://agentmods.dev/badge/skills/excalibuross/excalibur-core/testing.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.00022 | $0.00329 |
| Opus 5.5 | $0.00009 | $0.00132 |
| Sonnet 5.5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
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 2mo 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.
What it actually says
Testing skill
How to test QuickContract services correctly.
Instructions
- Co-locate unit specs in
test/as<name>.spec.ts, mirroringsrc/. - Build services with
Test.createTestingModulefrom@nestjs/testingand provide a mockedPrismaService— never connect to a real database in unit tests. - Mock Prisma model methods per test (
findUnique,create,update,findMany) withjest.fn()and assert on call arguments, not just call counts. - For webhook handlers, always include a retry case: deliver the same event twice and assert the side effect happened exactly once.
- Run the suite with
pnpm test; a focused file runs withpnpm test -- escrow.service.
Conventions
- Test names describe behavior:
releases funds once per captured payment. - Use integer cents in fixtures (
amountCents: 250_00). - Keep fixtures minimal; build helpers in the spec file, not shared globals.
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.
- 2mo ago First seen · 41 lines · 22 tokens per session scan A fb3c289ba1c6
testing is a skill published in the GitHub repository ExcaliburOSS/excalibur-core (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 329 once invoked, about $0.0001 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
adding-dbt-unit-test
Creates unit test YAML definitions that mock upstream model inputs and validate expected outputs. Use when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt.
cargo-pgrx
Choose and run cargo-pgrx commands, pgrx tests, pgtest coverage, and pgsys boundary checks.
blueprint-cloudflare-data
Turn the spec's tables into D1 migrations with tests.
jpa-persistence-test
Writes the persistence tests of a use case (UC-XXX) for Spring Data JPA: @DataJpaTest classes against a real database in a Testcontainers container (never H2 unless the project already tests on it), test data from Flyway test migrations, one UC RepositoryTest class per use case with @UseCase annotations. Tests only…
phpunit-migration-test-generation
Use this skill when the user asks to generate, write, or create migration tests for a Shopware 6 migration class — phrases like "generate migration tests", "write a migration test", "create migration test", "test this migration", "test Migration1234Foo". Analyzes the source migration's SQL operations to pick an…
synthetic-seeder
Generate two-sided synthetic data tests (source + Snowflake) for migrated stored procedures and functions. Derives test scenarios from source SQL branch analysis, writes step-based validation YAML artifacts, and enriches them with isolation metadata. Use when generating or refreshing test cases for a migrated object.…