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 agentmods add commands/pranav-karra-3301/tuck/testgit clone --depth 1 https://github.com/Pranav-Karra-3301/tuckWrote 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/pranav-karra-3301/tuck/test)<a href="https://agentmods.dev/commands/pranav-karra-3301/tuck/test"><img src="https://agentmods.dev/badge/commands/pranav-karra-3301/tuck/test.svg" alt="Measured on agentmods" 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.00004 | $0.00136 |
| Opus 5 | $0.00002 | $0.00068 |
| Sonnet 5 | $0.00001 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
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 6d 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
Test
Run the full test suite.
pnpm test
Test Watch
Run tests in watch mode (re-run on changes).
pnpm test:watch
Test Coverage
Run tests with coverage report.
pnpm test:coverage
Coverage report will be in coverage/ directory.
Test Single File
Run tests for a specific file.
pnpm test tests/lib/paths.test.ts
Test Pattern
Run tests matching a pattern.
pnpm test --grep "should handle"
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.
- 6d ago First seen · 46 lines · 4 tokens per session scan A a7069049f8b0
test is a command published in the GitHub repository Pranav-Karra-3301/tuck (15 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 136 once invoked, about $0.0000 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-30.
Other commands, from other repositories
upgrade-webkit
Upgrade Bun's WebKit fork to the latest upstream version of WebKit.
icon-lookup
Search for icons by name, or identify a PUA character.
dedupe
Find duplicate GitHub issues.
memory-store
Store an insight, decision, or pattern to memory.
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).
start
Runs a project that has already been compiled with vendure build.