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/jaemk/mind/releasenpx skills add jaemk/mind --skill releasegit clone --depth 1 https://github.com/jaemk/mindWhat 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.00042 | $0.01877 |
| Opus 5 | $0.00021 | $0.00938 |
| Sonnet 5 | $0.00008 | $0.00375 |
| Haiku 4.5 | $0.00004 | $0.00188 |
Grade A, and why
release 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 yesterday.
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release
Cut a tagged release of mind. The version in Cargo.toml is the single source
of truth: make release tags v<version> and pushes it, and that tag push
triggers .github/workflows/release.yml, which builds the per-platform binaries,
publishes the GitHub Release with the tarballs, and regenerates the Homebrew
formula.
Releases are SemVer. Pick the bump from what landed since the last tag: a new
verb/flag or other backward-compatible feature is a minor bump; a bug-fix-only
batch is a patch; a breaking change to the CLI, config, on-disk layout, or
mind.toml schema is a major bump.
Steps
1. Confirm a clean, green starting point
Work from main with everything merged and pushed.
git switch main && git pull
test -z "$(git status --porcelain)" || echo "tree is dirty; commit or stash first"
make ci # fmt-check + clippy (-D warnings) + test; must pass
2. Pick the version and survey the changes
git describe --tags --abbrev=0 # the previous release tag
git log "$(git describe --tags --abbrev=0)..HEAD" --format='%s'
Decide the new X.Y.Z from that list (see the SemVer note above).
3. Bump the version
Between releases main carries a pre-release version (X.Y.Z-dev) so a build
from main is distinguishable from the released binary. Drop the suffix here:
edit Cargo.toml [package].version to the new X.Y.Z, then sync the lockfile
so Cargo.lock's mind entry matches (the release build uses --locked, so a
stale lock fails CI):
cargo build # rewrites Cargo.lock's mind version
tests/changelog.rs only requires a matching ## [X.Y.Z] section once the
-dev suffix is gone, so this bump is what arms that check. Step 9 puts the
next -dev version back.
4. Update the changelog
Add a ## [X.Y.Z] - YYYY-MM-DD section at the top of CHANGELOG.md (Keep a
Changelog format), grouping the changes under Added / Changed / Fixed /
Removed. Describe user-facing behavior, not the commit workflow. Update the
link references at the bottom: point [Unreleased] at
.../compare/vX.Y.Z...HEAD and add [X.Y.Z]: .../compare/v<prev>...vX.Y.Z.
tests/changelog.rs enforces this (every version section needs a matching ref,
[Unreleased] must compare from the newest version, and each ref chains to the
next-older one), so make ci fails if a ref is missing or stale. Keep the voice
plain and factual (see ~/.local/share/agents/voice/voice-profile.md).
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.
- yesterday First seen · 165 lines · 42 tokens per session scan A 4a27fae8ec4d
release is a skill published in the GitHub repository jaemk/mind (1 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 1,877 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-31.
Other skills, from other repositories
baoyu-imagine
AI image generation with OpenAI GPT Image 2, Azure OpenAI, Google, OpenRouter, DashScope, Z.AI GLM-Image, MiniMax, Jimeng, Seedream and Replicate APIs. Supports text-to-image, reference images, aspect ratios, and batch generation from saved prompt files. Sequential by default; use batch parallel generation when the…
80-livekit-agents-majiayu000-claude-skill-registr
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
academy-guide
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude…
qa-manual-istqb
Create QA artifacts from requirements: test plans, test conditions/cases, bug reports, regression suites, traceability, and exploratory charters. Use for test planning, test design, defects, coverage, or QA deliverables. Applies ISTQB risk-based techniques and loads templates only when needed. Keywords: test plan…
a11y-playwright-testing
Accessibility testing for web applications using Playwright (@playwright/test), TypeScript, and axe-core. Use to write, run, or debug WCAG 2.2 AA checks, keyboard and focus tests, ARIA/semantic validation, accessible names, form labels, color contrast, or screen-reader test patterns. Keywords: accessibility, WCAG…
playwright-e2e-testing
Author and maintain versioned Playwright (@playwright/test) TypeScript UI specs for browser user flows. Use when asked to create, run, debug, or refactor E2E tests, form/navigation/auth flows, responsive checks, UI mocking, fixtures, Page Objects, or visual comparisons. Use api-testing for standalone REST/GraphQL…