Borrowing it
Nothing to install: this file belongs to wongo/my-minimax-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wongo/my-minimax-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/wongo/my-minimax-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/instructions/wongo/my-minimax-mcp/agents-md)<a href="https://agentmods.dev/instructions/wongo/my-minimax-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/wongo/my-minimax-mcp/agents-md.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.00551 | $0.00551 |
| Opus 5 | $0.00275 | $0.00275 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
my-minimax-mcp AGENTS.md 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 8d 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 — 20 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Core source lives in src/. src/mcp-server.ts is the stdio MCP entrypoint, src/cli.ts is the local debugging CLI, and feature code is grouped by concern: src/client/ for MiniMax API access, src/tools/ for MCP tool handlers, src/agent/ for the autonomous loop and safety checks, src/conversation/ for in-memory chat state, and src/utils/ for shared helpers. Build output goes to dist/. Root files of note: README.md, run-mcp.sh, and test-plan.md.
Build, Test, and Development Commands
Run npm install to install dependencies. Use npm run build to compile TypeScript into dist/ with tsc. Use npm run dev to start the MCP server directly from source with tsx src/mcp-server.ts. Use npm run cli to exercise the local CLI during development. Example: npx tsx src/cli.ts --mode agent --task "fix bug" --dir ./tmp-project.
Coding Style & Naming Conventions
This project uses strict TypeScript with ES modules and NodeNext resolution. Match the existing style: double quotes, semicolons, trailing commas where valid, and 2-space indentation. Prefer small, focused modules and named exports. Use camelCase for variables and functions, PascalCase for classes and types, and kebab-case for filenames such as generate-code.ts and cost-tracker.ts.
Testing Guidelines
There is no automated test runner configured yet: npm test currently exits with an error by design. Before opening a PR, at minimum run npm run build and manually verify the affected flow through npm run dev or npm run cli. Keep any future tests near the code they validate or add a dedicated tests/ directory, and name files with a clear .test.ts suffix.
Commit & Pull Request Guidelines
Recent history follows Conventional Commit prefixes such as feat:, fix:, docs:, and chore:. Keep commit subjects short and imperative, for example fix: enforce working-directory validation. PRs should explain the user-visible change, note config or env impacts, link the related issue when applicable, and include CLI or MCP usage examples when behavior changes.
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.
- 8d ago First seen · 20 lines · 551 tokens per session scan A 921a2b4e22a2
my-minimax-mcp AGENTS.md is an instructions file published in the GitHub repository wongo/my-minimax-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 551 tokens to every session, about $0.0028 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.