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 linxule/memex-plugin --skill project-consolidationgit clone --depth 1 https://github.com/linxule/memex-pluginWrote 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/linxule/memex-plugin/project-consolidation)<a href="https://agentmods.dev/skills/linxule/memex-plugin/project-consolidation"><img src="https://agentmods.dev/badge/skills/linxule/memex-plugin/project-consolidation/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/linxule/memex-plugin/project-consolidation"><img src="https://agentmods.dev/badge/skills/linxule/memex-plugin/project-consolidation.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.00133 | $0.02124 |
| Opus 5.5 | $0.00053 | $0.00850 |
| Sonnet 5.5 | $0.00027 | $0.00425 |
| Haiku 4.5 | $0.00013 | $0.00212 |
Grade C, and why
project-consolidation scanned grade C 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 28d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf projects/<from> How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portable copy of
skills/project-consolidation/SKILL.mdfor Codex and Kimi Code, generated byscripts/portable_plugin.py(do not edit here). Needs thememexCLI on PATH. Claude Code names (the Task/Agent tool,/memex:save, hooks) map to your host's equivalents.
Project-Folder Consolidation
Drifted project folders happen when session→project detection produced a
non-canonical name: a cwd-path fragment (Apps-arena instead of arena), or a
project split across folders (content under both personal-website and
linxule_com). The detection bugs that caused this were fixed in v0.15.5/v0.15.6
(detect_project via true session cwd + restored project_mappings), so no
new drift forms — this skill cleans up existing debt.
The cardinal rule
Never run memex obs reassign on a folder until you have confirmed it is a
duplicate or strict subset of the canonical target. A wrong merge collapses two
distinct projects. And never consolidate via git mv + memex index rebuild
— the incremental rebuild detects the old paths as deleted and cascade-deletes
the observations and their embeddings. obs reassign is the only safe primitive
(it UPDATEs doc_path in observations + chunks, preserving embeddings).
Step 1 — Audit
memex check --folders # human report: high-confidence drift + review list
memex check --folders --json # machine-readable, for planning
- High-confidence drift = cwd-fragment-shaped names, or content ⊆ another folder. Safe to act on after confirming duplication.
- Review (lower confidence) =
name≠canonical/ canonical collisions. The git remote or a memo's recordedcwdcan legitimately differ from a deliberately-chosen folder name (e.g. a real project whose folder ≠ its repo name). Verify manually; do not auto-act.
Step 2 — Confirm duplication (before touching anything)
Pick the canonical target — prefer the folder that already holds the most
observations and matches detect_project / project_mappings. Then prove the
source is redundant:
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.
- 28d ago Changed · +11 lines 0ce091d4c475
- 1mo ago First seen · 108 lines · 133 tokens per session scan C 4309f1683599
project-consolidation is a skill published in the GitHub repository linxule/memex-plugin (7 stars, last pushed yesterday), licensed MIT. It adds 133 tokens to every session and 2,124 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
roadmap-update
Produit un document de roadmap dans output/ en croisant l'état actuel des epics beads avec les décisions et priorités documentées dans le wiki. Applique les règles anti-lissage — ne jamais compléter avec des connaissances d'entraînement, citer le wiki pour chaque affirmation de scope ou de priorité. Triggers — mettre…
prd-os
PRD creation and PRD execution operating system. Use when the founder asks to turn a rough idea into a PRD, run a Codex review on a PRD or issue, decompose an approved PRD into issue specs, or execute an issue with scope enforcement and receipt-based closeout. Not for general product ideation or casual drafting; this…
report
Activity report from total-agent-memory for a project and period. Use when the user types /report or asks "report for today", "what did we do this week", "weekly / monthly summary", "status report", "retro for project X", "all-time report", "report for last week", or a report for a department or the whole company on…
ariadne:workstream-tracking
Create, audit, or improve Obsidian Kanban work boards and Dataview dashboards for durable project, roadmap, evaluation, implementation, QA, or recurring workstream tracking inside an agent-maintained vault.
project-flow-ops
Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
contrib-watch
Watch incoming feedback from outside engineers on your open-source repos: comments, reviews, issues, mentions. Use when you need to find who replied to your pull requests or issues, triage human versus bot responses, and answer within a day with evidence.