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/synmux/myriad/smitherygit clone --depth 1 https://github.com/synmux/myriadWrote 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/synmux/myriad/smithery)<a href="https://agentmods.dev/rules/synmux/myriad/smithery"><img src="https://agentmods.dev/badge/rules/synmux/myriad/smithery.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.00764 | $0.00764 |
| Opus 5 | $0.00382 | $0.00382 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
smithery 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smithery Registry API Documentation
Purpose: Programmatic access to search and obtain connection configurations for Model Context Protocol (MCP) servers.
Authentication
- Required: Bearer token in Authorization header
- Format:
Authorization: Bearer your-api-token - API key is stored in the
SMITHERY_API_KEYenvironment variable
Endpoints
1. List Servers
GET https://registry.smithery.ai/servers
Query Parameters
q: Search query (semantic search)page: Page number (default: 1)pageSize: Items per page (default: 10)
Filtering Syntax
- Text search:
"machine learning" - Owner filter:
owner:username - Repository filter:
repo:repository-name - Deployment status:
is:deployed - Combined example:
"owner:smithery-ai repo:fetch is:deployed machine learning"
Response Schema
{
servers: Array<{
qualifiedName: string;
displayName: string;
description: string;
homepage: string;
useCount: string;
isDeployed: boolean;
createdAt: string;
}>;
pagination: {
currentPage: number;
pageSize: number;
totalPages: number;
totalCount: number;
};
}
2. Get Server
GET https://registry.smithery.ai/servers/{qualifiedName}
Response Schema
{
qualifiedName: string;
displayName: string;
remote: boolean; // Whether the server is designed to run remotely or locally
iconUrl: string | null; // URL to the server's icon image, null if not set
deploymentUrl: string | null; // URL for deployed servers, null if not deployed
configSchema: JSONSchema; // Schema for server configuration
connections: Array<{
type: string;
url?: string;
configSchema: JSONSchema;
}>;
security: {
scanPassed: boolean;
} | null; // Added recently, null if no security scan performed
tools: Array<{
name: string;
description: string | null;
}> | null; // Added recently. List of tools provided by the server, null if not retrieved
}
```## Connection Details
- URL Format: `https://server.smithery.ai/${qualifiedName}/mcp?config=${base64encode(config)}&api_key=${smithery_api_key}`
- Config must comply with server's configSchema
- Config is base64-encoded JSON
- API key required for authentication
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 · 109 lines · 764 tokens per session scan A de8b164af1ff
smithery is a cursor rule published in the GitHub repository synmux/myriad (2 stars, last pushed yesterday), licensed MIT. It adds 764 tokens to every session, about $0.0038 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 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.