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/yodakeisuke/mcp-micromanage-your-agentWrote 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/yodakeisuke/mcp-micromanage-your-agent/solution-exploration-guide)<a href="https://agentmods.dev/rules/yodakeisuke/mcp-micromanage-your-agent/solution-exploration-guide"><img src="https://agentmods.dev/badge/rules/yodakeisuke/mcp-micromanage-your-agent/solution-exploration-guide/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/yodakeisuke/mcp-micromanage-your-agent/solution-exploration-guide"><img src="https://agentmods.dev/badge/rules/yodakeisuke/mcp-micromanage-your-agent/solution-exploration-guide.svg" alt="Reviewed on agentmods" width="80" 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.00007 | $0.00169 |
| Opus 5.5 | $0.00003 | $0.00068 |
| Sonnet 5.5 | $0.00001 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
solution-exploration-guide 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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- solution-exploration-guide — 100% identical, 0 lines differ
What it actually says
Purpose
- nformation gathering and Brainstorming potential approaches
Forbidden:
- Concrete planning, implementation details, or any code writing
##output-format
- file: ticket_[issue name].md
- chapters:
- Summary of the issue that will be resolved with the ticket
- Overview of the architecture, domain model and data model to be changed or added this time
- Work plan based on PR and commitment units(This is only for creating chapters, do not write content)
Method
- Understand the issue from the given information and existing code
- research and interviews with users to ensure that we have all the information we need to complete the task
- Analyze potential impacts to the existing codebase
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.
- 2mo ago First seen · 22 lines · 7 tokens per session scan A f3fe3e8f6989
solution-exploration-guide is a cursor rule published in the GitHub repository yodakeisuke/mcp-micromanage-your-agent (12 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 169 once invoked, about $0.0000 per session on Opus 5.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-30.
Other cursor rules, from other repositories
solve-blockers-proactively
When encountering a blocker, solve it or escalate; don't work around it.
bootstrap-alwayson
Minimal always-required LLM fixes.
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
error-handling-priorities
General rules for handling errors in code, including early checks, guard clauses, logging, user-friendly messages, and custom error types.
debugging
Debugging guidance for the Lineai MCP Server.
roslyn-mcp-pitfalls
Known pitfalls and regression lessons from production use.