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/Sahib-Sawhney-WH/sahibs-claude-plugin-marketplaceWrote 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/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/test)<a href="https://agentmods.dev/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/test"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/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/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/test"><img src="https://agentmods.dev/badge/commands/sahib-sawhney-wh/sahibs-claude-plugin-marketplace/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.00019 | $0.00590 |
| Opus 5 | $0.00010 | $0.00295 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
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 12d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DAPR Test Runner
Run tests for your DAPR application with proper mocking and integration support.
Behavior
When the user runs /dapr:test:
-
Detect Test Type
- Check for pytest configuration
- Identify test directories (tests/, test/)
- Determine test mode based on arguments
-
Configure Environment
- Set up DAPR test fixtures
- Configure mocking or real sidecar
- Prepare test components
-
Run Tests
- Execute pytest with DAPR fixtures
- Capture output and coverage
- Report results
Arguments
| Argument | Description |
|---|---|
unit |
Run unit tests with mocked DAPR client (default) |
integration |
Run integration tests with Testcontainers |
e2e |
Run end-to-end tests with real DAPR sidecar |
--coverage |
Generate coverage report |
--verbose |
Verbose output |
--filter |
Filter tests by pattern |
Test Modes
Unit Tests (Default)
/dapr:test unit
Uses mocked DAPR client for fast, isolated tests:
- No external dependencies
- Fastest execution
- Test business logic only
Integration Tests
/dapr:test integration
Uses Testcontainers for realistic testing:
- Redis container for state/pubsub
- Real component behavior
- Network isolation
End-to-End Tests
/dapr:test e2e
Uses real DAPR sidecar:
- Full DAPR runtime
- Production-like environment
- Slowest but most realistic
Test Structure
tests/
├── conftest.py # Shared fixtures
├── unit/
│ ├── test_state.py # State management tests
│ ├── test_pubsub.py # Pub/sub tests
│ └── test_service.py # Service invocation tests
├── integration/
│ └── test_e2e.py # Integration tests
└── docker-compose.test.yaml
Examples
Run All Unit Tests
/dapr:test
Run with Coverage
/dapr:test --coverage
Run Specific Test
/dapr:test --filter test_order_creation
Integration Tests
/dapr:test integration --verbose
Generated Files
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.
- 12d ago First seen · 114 lines · 19 tokens per session scan A 6c734198a11a
test is a command published in the GitHub repository Sahib-Sawhney-WH/sahibs-claude-plugin-marketplace (4 stars, last pushed 8mo ago), licensed MIT. It adds 19 tokens to every session and 590 once invoked, about $0.0001 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-31.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.