Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/titanzero/outlook-mcpnpx agentmods add rules/titanzero/outlook-mcp/testingWrote 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/rules/titanzero/outlook-mcp/testing)<a href="https://agentmods.dev/rules/titanzero/outlook-mcp/testing"><img src="https://agentmods.dev/badge/rules/titanzero/outlook-mcp/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/rules/titanzero/outlook-mcp/testing"><img src="https://agentmods.dev/badge/rules/titanzero/outlook-mcp/testing.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.00437 |
| Opus 5.5 | $0.00000 | $0.00175 |
| Sonnet 5.5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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.
What it actually says
Testing Rules
Framework
Jest (npm test). Tests live in test/ mirroring source structure:
email/list.js→test/email/list.test.jsauth/token-manager.js→test/auth/token-manager.test.js
Response Format in Tests
Tests assert against plain-text output. Set text mode at the top of every test file before imports:
process.env.OUTLOOK_RESPONSE_FORMAT = 'text';
Mock Pattern
Mock the Graph client and any module-level dependencies:
const { getGraphClient, graphGetPaginated } = require('../../utils/graph-client');
jest.mock('../../utils/graph-client');
const mockClient = {};
beforeEach(() => {
jest.clearAllMocks();
jest.spyOn(console, 'error').mockImplementation(() => {});
getGraphClient.mockResolvedValue(mockClient);
});
afterEach(() => {
console.error.mockRestore();
});
Assertion Style
- Check
result.content[0].textfor response content - Check
result.isErrorfor error responses - Verify mock call arguments with
expect.objectContaining()
Test Structure
Use nested describe blocks:
describe('handlerName', () => {
describe('successful operation', () => { ... });
describe('empty results', () => { ... });
describe('error handling', () => {
test('should handle authentication error', ...);
test('should handle Graph API error', ...);
});
});
Auth Error Testing
test('should handle authentication error', async () => {
const authError = new Error('Authentication required');
authError.isAuthError = true;
getGraphClient.mockRejectedValue(authError);
const result = await handler({});
expect(result.isError).toBe(true);
expect(result.content[0].text).toBe('Authentication required');
});
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 · 69 lines · 0 tokens per session scan A 08653d3a4ecf
testing is a cursor rule published in the GitHub repository titanzero/outlook-mcp (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 437 tokens. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
common-fixes
Utility for VAN QA common validation fixes.