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 skills add AVIDS2/memorix --skill memorix-troubleshootinggit clone --depth 1 https://github.com/AVIDS2/memorixWrote 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/skills/avids2/memorix/memorix-troubleshooting)<a href="https://agentmods.dev/skills/avids2/memorix/memorix-troubleshooting"><img src="https://agentmods.dev/badge/skills/avids2/memorix/memorix-troubleshooting/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/skills/avids2/memorix/memorix-troubleshooting"><img src="https://agentmods.dev/badge/skills/avids2/memorix/memorix-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00335 |
| Opus 5 | $0.00018 | $0.00168 |
| Sonnet 5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
memorix-troubleshooting 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 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.
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
Memorix Troubleshooting
Prefer direct CLI diagnostics first. MCP is an integration surface, not the only way to operate Memorix.
Diagnostic Router
| Symptom | Check | CLI fallback |
|---|---|---|
| MCP tools missing | host MCP config and restart | memorix setup --agent <agent> |
| Unsure project is bound | project status | memorix status and git status |
| HTTP MCP stale or unbound | background health and explicit session bind | memorix background status; then memorix session start --projectRoot <path> |
| Hooks not firing | hook status | memorix hooks status |
| Need to inspect generated files | preview | memorix hooks preview --agent <agent> |
| Setup looks incomplete | reinstall host integration | memorix setup --agent <agent> |
| Need dashboard/control plane | background service | memorix background start or memorix serve-http --port 3211 |
Mode Rules
- Use stdio MCP (
memorix serve) for normal host-launched MCP integration. - Use HTTP/background only for shared endpoint, dashboard, Docker, multiple clients, or foreground control-plane debugging.
- On Windows, prefer absolute native paths for
projectRootand remember that visually similar junction paths may bind different session histories. - If MCP is unavailable but the CLI works, continue through CLI commands instead of blocking.
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 · 28 lines · 36 tokens per session scan A 5375ee983a13
memorix-troubleshooting is a skill published in the GitHub repository AVIDS2/memorix (738 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 335 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
post-mortem
Diagnose instruction defects and optionally submit Rosetta GitHub issue.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
solr-query
To build and debug Solr queries: eDisMax, block join, JSON facets, kNN, explain.