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/tchivs/aktools-pro/cursorrulesgit clone --depth 1 https://github.com/tchivs/aktools-proWhat 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.00314 | $0.00314 |
| Opus 5 | $0.00157 | $0.00157 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
cursorrules 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 yesterday.
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
mcp-aktools AI Coding Rules
๐ค Model Specific Instructions
- Codex/Copilot: Focus on PEP 8, Type Hints, and strict return types. Use
ruffpatterns for code fixes. - Claude Code: Prioritize updating MCP
@mcp.tooldescriptions. Maintain CSV return formats. - OpenCode/Sisyphus: Follow the SOPs defined in
AGENTS.md. Always classify tasks intoquick,ultrabrain, orvisual-engineering.
๐ Tech Stack
- Framework: FastMCP (Python)
- Data: akshare
- Formatting: Ruff
๐ Coding Standards
- Naming:
snake_casefor everything except classes (PascalCase). - Tool Definitions:
- Every tool must have
titleanddescriptionin@mcp.tool. - Parameters must use
pydantic.Fieldwith descriptions.
- Every tool must have
- Data Flow:
- All data-fetching must use
ak_cache. - Returns must be
str(usually CSV viadf.to_csv()).
- All data-fetching must use
- Types: Always include type hints for new functions. Use
pd.DataFrame | Nonefor data-related returns.
๐ซ Anti-Patterns
- No raw JSON/List returns for MCP tools.
- No direct
aksharecalls withoutak_cache. - No suppression of type errors with
# type: ignoreunless absolutely necessary.
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.
- yesterday First seen ยท 27 lines ยท 314 tokens per session scan A eb6437566e5d
cursorrules is a cursor rule published in the GitHub repository tchivs/aktools-pro (5 stars, last pushed 7mo ago), licensed MIT. It adds 314 tokens to every session, about $0.0016 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other cursor rules, from other repositories
binance-net
Conventions for using Binance.Net library when working with Binance cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with Binance API.
kraken-net
Conventions for using Kraken.Net when working with Kraken Spot and Futures cryptocurrency exchange APIs in C#/.NET. Apply when generating code that interacts with Kraken API.
hyperliquid-net
Conventions for using HyperLiquid.Net when working with the HyperLiquid DEX in C#/.NET, including spot, futures, account, HIP-3 DEX, and HIP-4 outcome APIs. Apply when generating code that interacts with the HyperLiquid API.
whitebit-net
Conventions for using WhiteBit.Net when working with the WhiteBit cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with WhiteBit APIs.
xt-net
Conventions for using the XT.Net library when working with the XT cryptocurrency exchange in C#/.NET. Apply when generating code that interacts with the XT API.
development-workflow
This project uses pnpm for package management and has a structured set of scripts for different development tasks.