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 agents/0xfurai/claude-code-subagents/jasmine-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/jasmine-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/jasmine-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/jasmine-expert.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 | $0.00055 | $0.00555 |
| Opus 5 | $0.00028 | $0.00278 |
| Sonnet 5 | $0.00011 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
jasmine-expert 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Understanding Jasmine test suite and spec structure
- Writing descriptive test cases and using matchers effectively
- Asynchronous testing with done(), async/await, and promises
- Utilizing spies for mocking and tracking function calls
- Best practices for organizing test files and suites
- Sequential and parallel test execution configurations
- Test-driven development (TDD) methodologies with Jasmine
- Handling setup and teardown using beforeAll/afterAll and beforeEach/afterEach
- Ensuring comprehensive test coverage with effective use of tools
- Integration with continuous integration pipelines
Approach
- Define clear and concise test suites with meaningful descriptions
- Break down large test files into smaller, modular test files
- Write tests that are independent and easy to understand
- Use custom matchers to express expectations more clearly
- Apply the Arrange-Act-Assert (AAA) pattern consistently in tests
- Focus more on edge cases and boundary conditions
- Ensure tests are deterministic and produce the same result every time
- Use Spies to replace complex dependencies and isolate the unit under test
- Keep test feedback fast to ensure quick iteration cycles
- Regularly refactor tests for clarity and maintainability
Quality Checklist
- Verify all test cases are passing consistently without flakiness
- Ensure test descriptions clearly communicate intent
- Verify use of appropriate Jasmine matchers for different scenarios
- Confirm asynchronous code is properly handled in tests with done() or async/await
- Review spy usage to ensure accurate and minimal implementation
- Validate test setup and teardown correctly reset state before each test
- Run tests in random order to detect implicit dependencies
- Check for redundant or duplicate tests and eliminate them
- Perform code coverage analysis to identify untested code paths
- Ensure tests are well-documented and easy to read
Output
- Comprehensive and organized test suite using Jasmine framework
- Test cases covering edge cases and all potential failure points
- Clean and deterministic tests with accurate setup and teardown
- High test coverage with minimal false negatives or positives
- Well-documented tests with clear naming conventions and structure
- Configurable test environment suited for both development and CI pipelines
- Efficient test execution with both sequential and parallel options
- Jasmine spy reports and mock functionality for dependency isolation
- Automated test results integrated with continuous integration systems
- Continuous improvement and refactoring of test code based on feedback
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.
- 4d ago First seen · 63 lines · 55 tokens per session scan A 08230f47a405
jasmine-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 55 tokens to every session and 555 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.