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 instructions/robertzaufall/mindm-skill/agents-mdgit clone --depth 1 https://github.com/robertZaufall/mindm-skillWhat 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.00386 | $0.00386 |
| Opus 5 | $0.00193 | $0.00193 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
mindm-skill AGENTS.md 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 2d 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
Agent Notes
Key Rules
- Source of truth is
skills/. Do not editmindm/skills/*.skillby hand. - After any skill change, run
make packageto regenerate bundles. - Use
make listto verify which skills will be packaged. - Keep skill folders lean (SKILL.md plus needed references/assets only).
Build Commands
make package # Build all skill bundles
make list # List available skills
make validate # Validate skill definitions
make checksums # Generate SHA256 checksums
make clean # Remove packaged bundles
Packaging uses zip -r -X for stable bundles and excludes *.DS_Store and __MACOSX.
Adding a Skill
- Create a folder at
skills/<name>/withSKILL.md - Add optional assets or references under that folder
- Run
make validateto check the skill definition - Run
make packageto generatemindm/skills/<name>.skill
SKILL.md Format
Each skill requires a SKILL.md with YAML frontmatter:
---
name: my-skill
description: One-line description of what the skill does.
version: 1.0.0
requires:
- package-name
platforms:
- macos
- windows
---
# Skill Title
Markdown content with usage instructions...
Required fields: name, description
Recommended fields: version, requires, platforms
Directory Structure
skills/ # Source skill definitions (editable)
mindm-mindmap/
SKILL.md
references/
mindm-export/
SKILL.md
references/
mindm/skills/ # Packaged .skill bundles (generated)
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.
- 2d ago First seen · 65 lines · 386 tokens per session scan A d22ba83672d4
mindm-skill AGENTS.md is an instructions file published in the GitHub repository robertZaufall/mindm-skill (5 stars, last pushed 7mo ago), licensed MIT. It adds 386 tokens to every session, about $0.0019 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-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.