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 agentmods add skills/volomydyr/design-engineer-plugin/meta-documentnpx skills add volomydyr/design-engineer-plugin --skill meta-documentgit clone --depth 1 https://github.com/volomydyr/design-engineer-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/volomydyr/design-engineer-plugin/meta-document)<a href="https://agentmods.dev/skills/volomydyr/design-engineer-plugin/meta-document"><img src="https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/meta-document.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 | $0.00060 | $0.03071 |
| Opus 5 | $0.00030 | $0.01536 |
| Sonnet 5 | $0.00012 | $0.00614 |
| Haiku 4.5 | $0.00006 | $0.00307 |
Grade A, and why
meta-document 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
meta-document Skill
Purpose: Document solutions, store project status, and maintain living context files that enable long-term complex projects across sessions, chat compaction, and team handoffs.
Overview
After any significant work is completed (a design deliverable, a development phase, a psychology audit), this skill captures what was done, what worked, what did not work, and what comes next. It maintains a structured project status file that AI reads at the start of every task, reducing hallucinations and preventing repeated mistakes.
This is not for pet projects that you start and abandon. This is for actual complex projects planned to run for years, potentially becoming million-dollar products with multiple teams working on them.
Organization: Each documentation entry is a markdown file with validated YAML frontmatter, stored in .design-engineer-plugin/design/dev/[category]/. Live progress (current phase, key decisions, stale dependents) is tracked separately by the compound-documenter agent in its project-local memory at .claude/agent-memory/design-engineer-compound-documenter/ – Anthropic's documented persistence primitive for subagents.
<critical_sequence name="compound-documentation" enforce_order="strict">
6-Step Process
Auto-invoke after:
- Completion of any pipeline phase (pre-dev, dev, psychology audit)
- User confirms a solution worked ("that fixed it", "looks good", "approved")
- End of any complex multi-step task
OR manual: /design-engineer:document command
Document when:
- A design deliverable was produced or significantly revised
- A development phase completed
- A non-obvious solution was found after multiple attempts
- Decisions were made that future sessions need to know about
- Context that would be lost to chat compaction
Skip documentation for:
- Trivial edits (typo fixes, formatting changes)
- Intermediate work that will be superseded
- Information already captured in existing deliverables
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 372 lines · 60 tokens per session scan A 512cd1a058ed
meta-document is a skill published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 3,071 once invoked, about $0.0003 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
neuron-rag-specialist
Implement RAG (Retrieval-Augmented Generation) with Neuron AI including vector stores, embeddings providers, document loaders, and retrieval strategies. Use this skill whenever the user mentions RAG, retrieval, vector search, document retrieval, semantic search, knowledge bases, chat with documents, or wants to build…
knowledge-distillation
Compile one or more OpenViking knowledge bases or document collections into topic-organized, evidence-grounded high-level knowledge, including cross-source findings, trends, changes, drivers, comparisons, implications, and uncertainties. Use with ov compile when the user asks to distill or synthesize a knowledge base…
mindos-zh
MindOS 是用户的本地知识助手，也是跨会话、跨 Agent 共享的知识库。它保存决策记录、会议纪要、SOP、 排错经验、架构选型、调研结论和偏好设置。 仅 mindRoot 知识库内任务。不用于：改代码仓库、项目源码、KB 外路径。 核心概念：空间、指令(INSTRUCTION.md)、技能(SKILL.md)；笔记可承载指令与技能。 触发场景：保存或记录任何内容、搜索历史笔记或上下文、更新或编辑文件、整理或重组文件结构、 执行SOP或工作流、捕获对话中的决策、复盘或总结经验、追加表格或CSV数据、跨Agent交接上下文、 提炼经验教训、同步关联文档、查找之前是否讨论过某事、查询历史决策、查找模板或SOP、…
mindos
Operate a MindOS knowledge base: update notes, search, organize files, execute SOPs/workflows, retrospective, append CSV, cross-agent handoff, route unstructured input to the right files, distill experience, sync related docs. Use when the task targets files inside the user's MindOS KB (mindRoot). NOT for editing app…
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
n8n-binary-and-data-official
Use when handling files, images, attachments, or binary data in n8n, OR when an AI agent needs to take a user-uploaded file as tool input or return a generated file. For Data Tables (schemas, dedup, persistent state), see the separate n8n-data-tables-official skill. Triggers on "file", "image", "PDF", "attachment"…