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/SecretRichGarden/metasota-API-MCPWrote 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/secretrichgarden/metasota-api-mcp/project-structure)<a href="https://agentmods.dev/rules/secretrichgarden/metasota-api-mcp/project-structure"><img src="https://agentmods.dev/badge/rules/secretrichgarden/metasota-api-mcp/project-structure.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.1 | $0.00408 | $0.00408 |
| Opus 5 | $0.00204 | $0.00204 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
project-structure 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 7d 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
Metaso Search MCP Project Structure
This is a Node.js/TypeScript project implementing a Model Context Protocol (MCP) server for Metaso Search API integration.
Project Overview
- Type: MCP Server (stdio transport)
- Language: TypeScript (ES2022, Node16 modules)
- Main Entry:
src/index.ts(compiled todist/index.js) - Package Manager: npm
- Key Dependencies:
@modelcontextprotocol/sdk- MCP protocol implementationaxios- HTTP client for API callszod- Schema validation
Project Structure
metasota_API_MCP/
├── src/ # TypeScript source files
│ └── index.ts # Main MCP server entry point
├── dist/ # Compiled JavaScript (generated)
├── docs/ # Documentation
│ ├── # 秘塔搜索MCP工具开发完整方案.md
│ └── 秘塔搜索API所有功能整理.md
├── .cursor/rules/ # Cursor rules
├── package.json # Project configuration
└── tsconfig.json # TypeScript configuration
Key Configuration
- API Endpoint:
https://metaso.cn/api/v1 - Authentication: Bearer token via
METASO_API_KEYenvironment variable - Transport: stdio (for MCP communication)
- Module System: ES Modules (
"type": "module")
Development Workflow
- Source code in
src/directory - TypeScript compiles to
dist/directory - Use
npm run buildto compile - Use
npm startto run compiled code - Binary entry point:
dist/index.js(viabinin package.json)
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.
- 7d ago First seen · 44 lines · 408 tokens per session scan A 65466b16009b
project-structure is a cursor rule published in the GitHub repository SecretRichGarden/metasota-API-MCP (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 408 tokens to every session, about $0.0020 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.