mindm-skill AGENTS.md

Repository instructions for mindm-skill, a project that packages coding-agent skills into distributable files.

In plain words
What is it for?
Adding or editing skills, validating their format, listing package contents, rebuilding bundles, and generating checksums.
Why use it?
They identify the source files, build commands, validation checks, and packaging rules needed to change a skill safely.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/robertzaufall/mindm-skill/agents-md
Clone the repo
git clone --depth 1 https://github.com/robertZaufall/mindm-skill

Made for: Codex, OpenCode.

Per session 386 This file is loaded in full into every session.
When invoked 386 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash d22ba83672d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

AGENTS.md · 65 lines

What it actually says

Agent Notes

Key Rules

  • Source of truth is skills/. Do not edit mindm/skills/*.skill by hand.
  • After any skill change, run make package to regenerate bundles.
  • Use make list to 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

  1. Create a folder at skills/<name>/ with SKILL.md
  2. Add optional assets or references under that folder
  3. Run make validate to check the skill definition
  4. Run make package to generate mindm/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)
Changes

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.

  1. 2d ago First seen · 65 lines · 386 tokens per session scan A d22ba83672d4

Subscribe to this mod's changes

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.

Related

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.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens