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/Ikalus1988/MisakaNetWrote 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/ikalus1988/misakanet/misakanet-failure-memory)<a href="https://agentmods.dev/rules/ikalus1988/misakanet/misakanet-failure-memory"><img src="https://agentmods.dev/badge/rules/ikalus1988/misakanet/misakanet-failure-memory.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.00000 | $0.00617 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
misakanet-failure-memory scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS https://misakanet.org/mcp \ How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MisakaNet Failure Memory
When a command, test, CI, DCO, token, pip, MCP, or Windows encoding issue fails, search MisakaNet before attempting a fix from general knowledge.
When to trigger
- Command exits with non-zero status
- Test fails with an error message
- CI/CD pipeline fails
- DCO sign-off check fails
- GitHub token / authentication errors
- pip install timeout or SSL errors
- MCP server connection issues
- Windows encoding (GBK/Unicode) errors
- Database locked / SQLite errors
- Docker build failures
Steps
-
Search MisakaNet with the error message or key terms:
misakanet_search(query="<error message or key terms>") -
Read the matching lesson if results are returned:
misakanet_get_lesson(path="<lesson path from search results>") -
Apply only the relevant fix from the lesson. Do not invent fixes beyond what the lesson describes.
-
If no match found, submit a redacted intake via MCP (no GitHub account needed):
curl -sS https://misakanet.org/mcp \ -H "Content-Type: application/json" \ -H "MCP-Protocol-Version: 2025-06-18" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"misakanet_submit_intake","arguments":{"problem":"<short error description>","source":"cursor"}}}'
What NOT to do
- Do not skip MisakaNet search for known failure patterns (DCO, token, pip, MCP, encoding)
- Do not upload raw logs, prompts, or secrets to MisakaNet
- Do not auto-retry more than twice without searching MisakaNet
- Do not apply fixes from MisakaNet lessons to unrelated problems
MCP Tools Available
| Tool | Auth | Purpose |
|---|---|---|
misakanet_search |
≤5 free/day remote | Search lessons |
misakanet_get_lesson |
≤5 free/day remote | Get lesson content |
misakanet_submit_intake |
No auth needed | Submit failure case |
misakanet_submit_usage |
No auth needed | Submit usage feedback |
Example
User: "My pytest is failing with ImportError"
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.
- 9d ago First seen · 76 lines · 0 tokens per session scan A ab9183939630
misakanet-failure-memory is a cursor rule published in the GitHub repository Ikalus1988/MisakaNet (466 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 617 tokens. A static security scan graded it A with 1 finding (makes network calls). 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
hatch3r-dynamic-stack-verification
Runtime-evidence gates for stacks with no static type layer (plain-JS Vue, dynamic persistence) — smoke-mount changed components, dormant-collection-read ratchet, runtime smoke evidence on module-boundary changes; a green lint+build+mock-suite proves a layer, not the system.
debug-capture-pipeline
Debug llm-wiki-memory capture/recall — flush breadcrumbs, daily-vs-compile lag, failed-distill stash recovery, embedding cache, hook wiring. Use when memory didn't capture, doesn't recall, or a hook/cron looks broken.
pi-en
PI Cognitive AI. Trigger: $pi/coding/dev/code/architecture/API/refactor/debug/bug/error/exception/crash/timeout/performance/optimization/test/compile/git/release/verify/review/CR/product/requirements/ops/growth/design/team/support, or deep/2+ failures/looping/stuck/giving-up/retry/nevermind.
hatch3r-observability-logging
Structured logging and error reporting conventions for the project.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
decision-logger
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting…