mimocode-docs
Use whenever the user asks about MiMoCode itself: features, TUI or CLI commands, configuration, file locations, providers, models, authentication, or custom OpenAI-compatible or Anthropic-compatible API endpoints. Especially trigger when a prompt supplies or asks to configure a base URL/baseURL, API key/apiKey, model name or ID, provider, Anthropic Messages API, or global/project mimocode.json/jsonc. Use this skill to inspect existing config safely, make minimal changes, and verify them without guessing schema fields or model capabilities.
77
96%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The skill’s required workflow is file-based agent configuration (and dynamic workflow scripts) where MiMoCode reads Markdown/JS from project/global/user-provided directories; if an outsider contributed those files, their text would be injected into the LLM context via the system-prompt/body for agents/modes or via workflow/child-workflow prompts/results at runtime.
- Repository
- XiaomiMiMo/MiMo-Code
- Commit
ff87d47
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.