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 filipebraida/adonisjs-starter-kit --skill testinggit clone --depth 1 https://github.com/filipebraida/adonisjs-starter-kitWrote 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/filipebraida/adonisjs-starter-kit/testing)<a href="https://agentmods.dev/skills/filipebraida/adonisjs-starter-kit/testing"><img src="https://agentmods.dev/badge/skills/filipebraida/adonisjs-starter-kit/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/filipebraida/adonisjs-starter-kit/testing"><img src="https://agentmods.dev/badge/skills/filipebraida/adonisjs-starter-kit/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.00082 | $0.02158 |
| Opus 5.5 | $0.00033 | $0.00863 |
| Sonnet 5.5 | $0.00016 | $0.00432 |
| Haiku 4.5 | $0.00008 | $0.00216 |
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 1mo 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Two suites: unit for action/service internals with dependencies stubbed; functional for HTTP endpoints hit against a real Postgres wrapped in a per-test transaction. Every spec matches the shape of the nearest existing spec — same imports, same setup/teardown order, same helpers. Anything that reaches out (mail, drive, emitter, transmit, third-party HTTP) must be faked; a global mail fake in tests/bootstrap.ts is a safety net so a forgotten setup doesn't send a real email.
Mandatory fakes by dependency
Every side-effect dependency needs an explicit fake so no test reaches real infra:
| Dependency | How to fake | Scope |
|---|---|---|
mail.fake() |
Global in tests/bootstrap.ts + per-test when asserting |
|
| Drive | drive.fake(env.get('DRIVE_DISK') ?? 'fs') |
Per-group setup + teardown |
| Emitter | emitter.fake(['event:name']) → EventsBuffer |
Per-test opt-in |
| Transmit (SSE) | transport: null in config/transmit.ts (default) |
Global |
emitter.fake takes an array of event names — a bare string is a TypeScript error:
const events = emitter.fake(['user:registered']) // ✅
// emitter.fake('user:registered') // ❌ wrong type
Rules
- Location:
app/<mod>/tests/{unit,functional}/*.spec.ts. - Group setup: every group opens with
group.each.setup(() => testUtils.db().wrapInGlobalTransaction())when the code under test touches DB (nearly always). - RBAC helpers: functional specs involving roles/permissions call
group.each.setup(() => ensureBaseRoles()); assign per user withwithRole(user, ROLES.X)/withPermissions(user, [...]). - Emitter fake: to isolate an endpoint from its listeners,
const fake = emitter.fake(['event:name'])in setup +emitter.restore()in teardown. Assert withfake.assertEmitted('event:name')/fake.assertNoneEmitted(). - Mail fake:
const mails = mail.fake()in the test, thenmails.assertSent(Notification, (msg) => ...)ormails.assertNoneSent(). - Drive fake:
drive.fake(...)in group setup,drive.restore(...)in teardown. Assert withdisk.assertExists(path),disk.assertMissing(path). - Sinon for stubbing services, drivers, and single functions in unit tests:
sinon.stub<[Arg], Promise<Ret>>().resolves(...). Alwaysgroup.each.teardown(() => sinon.restore()). - Factories over fixtures — use
UserFactory.create()/UserFactory.merge({...}).create()instead of hand-building rows. - CSRF: POST/PUT/DELETE must include
.withCsrfToken()— shield middleware is enforced. - Auth: use
.loginAs(user)on the request builder — sets the session cookie for that user's guard. - JSON vs HTML: chain
.accept('json')when asserting a JSON response body,.withInertia()for Inertia flows so the exception handler treats the request as UI. - DB assertions:
db.assertHas('table', { column: value }),db.assertMissing('table', { ... })— plugin from@adonisjs/lucid/plugins/db.
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.
- 1mo ago First seen · 185 lines · 82 tokens per session scan A 3a93cb60ed27
testing is a skill published in the GitHub repository filipebraida/adonisjs-starter-kit (96 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 2,158 once invoked, about $0.0003 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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
06-test
Write and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use for independent acceptance QA or reviewer evidence, auditing test health, or…