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.
git clone --depth 1 https://github.com/go4cas/quiverWrote 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/commands/go4cas/quiver/add-test)<a href="https://agentmods.dev/commands/go4cas/quiver/add-test"><img src="https://agentmods.dev/badge/commands/go4cas/quiver/add-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/commands/go4cas/quiver/add-test"><img src="https://agentmods.dev/badge/commands/go4cas/quiver/add-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.00000 | $0.00716 |
| Opus 5.5 | $0.00000 | $0.00286 |
| Sonnet 5.5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
add-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 27d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write tests for: $ARGUMENTS
The argument is a file path (e.g. src/pages/users/index.js, src/composables/useForm.js, src/framework/router.js).
Follow this process:
Step 1 — Determine test type
| Source location | Test type | Output location |
|---|---|---|
src/framework/*.js |
Unit (Vitest) | tests/framework/<name>.test.js |
src/composables/*.js |
Unit (Vitest) | tests/composables/<name>.test.js |
src/pages/**/*.js |
E2E (Playwright) | tests/e2e/<name>.test.js |
src/components/*.js |
E2E (Playwright) | tests/e2e/<name>.test.js |
src/state/*.js |
Unit (Vitest) | tests/composables/<name>.test.js |
If an existing test file for this source already exists, extend it rather than creating a new one.
Step 2 — Write unit tests (Vitest)
import { describe, it, expect, beforeEach } from 'vitest'
import { functionUnderTest } from '../../src/path/to/file.js'
describe('functionUnderTest', () => {
it('does the expected thing', () => {
expect(functionUnderTest(input)).toBe(expectedOutput)
})
it('handles edge case', () => {
expect(functionUnderTest(edgeInput)).toBe(edgeOutput)
})
})
- Test pure function behaviour and edge cases
- Use
beforeEachto reset any shared state between tests - Do not mock framework internals unless unavoidable
Step 3 — Write E2E tests (Playwright)
import { test, expect } from '@playwright/test'
test.describe('FeatureName', () => {
test.beforeEach(async ({ page }) => {
await page.goto('/')
})
test('happy path', async ({ page }) => {
await page.getByRole('link', { name: 'Nav link' }).click()
await expect(page).toHaveURL(/\/expected-path/)
await expect(page).toHaveTitle('Expected Title')
await expect(page.getByRole('heading', { name: 'Heading' })).toBeVisible()
})
})
- Prefer role-based selectors:
getByRole,getByLabel,getByText - Use
getByTestIdfor elements with no semantic role; adddata-testidattributes to the source if needed - Cover: happy path, key edge cases, error states where applicable
- Do not test implementation details — test what the user sees and can do
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.
- 27d ago Changed 527303f5e15f
- 1mo ago First seen · 74 lines · 0 tokens per session scan A 23e4e1d1add6
add-test is a command published in the GitHub repository go4cas/quiver (5 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 716 tokens. 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 commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
gsd:add-tests
Generate tests for a completed phase based on UAT criteria and implementation.
e2e-testing
:::info The Playwright suite launches the real Electron main process and built React UI on Windows and macOS. It exercises the preload bridge, IPC handlers, and file storage. See Testing Commands for the separate Vitest suite. ::.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
test
Load the testing strategies skill for 3-tier testing with NO MOCKING policy enforcement in Tier 2-3.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.