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 commands/404-not-found/mindlink/profilegit clone --depth 1 https://github.com/404-not-found/mindlinkWhat 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.00000 | $0.00674 |
| Opus 5 | $0.00000 | $0.00337 |
| Sonnet 5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
profile 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mindlink profile
Manage your global user profile — imported into every new project automatically.
Synopsis
mindlink profile [--show] [--path]
Description
Your global user profile lives at ~/.mindlink/USER.md. It stores personal facts about you — role, experience, preferences, communication style — that are true regardless of which project you're working in.
When you run mindlink init on a new project, your profile is automatically imported into the ## User Profile section of .brain/MEMORY.md. Your AI starts the first session already knowing who you are.
When you run mindlink update, the profile is synced to all registered projects — any changes you make are propagated everywhere.
Commands
Open profile in your $EDITOR:
mindlink profile
Print profile to stdout:
mindlink profile --show
Print profile file path:
mindlink profile --path
Profile Format
# MindLink — Global User Profile
> This file is imported into every new project's MEMORY.md on `mindlink init`.
> Edit it with `mindlink profile`. Run `mindlink update` to sync changes to all projects.
Senior full-stack engineer, 8 years. Primary: TypeScript, Python.
Prefers functional patterns, minimal abstraction.
Direct communication — skip preamble, lead with the answer.
macOS + zsh. Editor: VS Code + Claude Code.
<!-- added: 2026-04-13 -->
Write anything your AI should know about you in plain Markdown. The more specific, the better — role, experience level, communication preferences, tools, and how you like problems explained.
How It Works
- On
mindlink init: if~/.mindlink/USER.mdexists with real content, it is injected into the## User Profilesection of the new project'sMEMORY.md. - On
mindlink update: the current profile replaces the## User Profilesection in all registered projects — keeping them in sync as your profile evolves.
Options
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 · 105 lines · 0 tokens per session scan A 3e24222db04f
profile is a command published in the GitHub repository 404-not-found/mindlink (11 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 674 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.