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 rules/marcushojww/tableau-mcp-v2/toolsgit clone --depth 1 https://github.com/marcushojww/tableau-mcp-v2Wrote 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/marcushojww/tableau-mcp-v2/tools)<a href="https://agentmods.dev/rules/marcushojww/tableau-mcp-v2/tools"><img src="https://agentmods.dev/badge/rules/marcushojww/tableau-mcp-v2/tools.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.00000 | $0.00886 |
| Opus 5 | $0.00000 | $0.00443 |
| Sonnet 5 | $0.00000 | $0.00177 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
tools 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.
This is a copy
97% identical to tools — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tool Development Patterns
Factory Pattern
Every tool exports a factory function registered in src/tools/tools.ts:
export const getMyTool = (server: Server): Tool<typeof paramsSchema> => {
const myTool = new Tool({
server,
name: 'my-tool', // Must be in ToolName union (src/tools/toolName.ts)
description: '...',
paramsSchema, // Zod schema object (not z.object, just raw shape)
annotations: { title: 'My Tool', readOnlyHint: true, openWorldHint: false },
callback: async (args, extra) => { ... },
});
return myTool;
};
Adding a New Tool — Checklist
- Add tool name to
toolNamesarray insrc/tools/toolName.ts - Add to appropriate
toolGroupsentry (or create new group) - Add scope mapping in
src/server/oauth/scopes.ts(toolScopeMap) - Create tool directory under
src/tools/ - Implement factory function following the pattern above
- Register factory in
src/tools/tools.ts(toolFactoriesarray)
Tool Callback Pattern
Callbacks use logAndExecute from the base Tool class:
callback: async (args, extra): Promise<CallToolResult> => {
return await myTool.logAndExecute({
extra,
args,
callback: async () => {
const result = await useRestApi({
...extra,
jwtScopes: myTool.requiredApiScopes,
callback: async (restApi) => {
// Use restApi methods here
return data;
},
});
return new Ok(result); // ts-results-es Ok()
},
constrainSuccessResult: (result) => constrainMyResult(result),
});
},
Result Types
Result<T, E>fromts-results-es— tool callbacks return thisOk(value)for success,Err(error)for typed errorsConstrainedResult<T>— post-processing step with three outcomes:{ type: 'success', result: T }— data returned to client{ type: 'empty', message: string }— no data found (not an error){ type: 'error', message: string, error?: Error }— logical error
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 · 98 lines · 0 tokens per session scan A cc3087876605
tools is a cursor rule published in the GitHub repository marcushojww/tableau-mcp-v2 (0 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 886 tokens. A static security scan graded it A with 0 findings. It is 97% identical to tools, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.