Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/markmhendrickson/neotomanpx agentmods add commands/markmhendrickson/neotoma/setup_commandsWrote 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/commands/markmhendrickson/neotoma/setup_commands)<a href="https://agentmods.dev/commands/markmhendrickson/neotoma/setup_commands"><img src="https://agentmods.dev/badge/commands/markmhendrickson/neotoma/setup_commands/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/markmhendrickson/neotoma/setup_commands"><img src="https://agentmods.dev/badge/commands/markmhendrickson/neotoma/setup_commands.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00660 |
| Opus 5.5 | $0.00000 | $0.00264 |
| Sonnet 5.5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
setup_commands 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Foundation Commands Only
Sets up symlinks from foundation cursor commands to .cursor/commands/. Does not link or change rules.
Command
setup_commands
or
setup commands
Purpose
This command runs foundation/scripts/setup_cursor_commands.sh, which:
- Creates symlinks from
foundation/agent_instructions/cursor_commands/to.cursor/commands/ - Uses original filenames (no prefix)
- Removes existing foundation command symlinks before creating new ones
- Preserves non-symlink files (e.g. repo-specific commands like
migrate_plans.md) - Does not touch
.cursor/rules/or repo rules fromdocs/
Use this when you only want foundation commands (e.g. commit, pull, push) without linking rules. Use /setup_symlinks to link both rules and commands.
When to Use
- When you want foundation commands (commit, pull, push, etc.) but keep repo-specific rules
- After updating the foundation submodule and you only need commands refreshed
- When rules are managed separately (e.g. via setup_cursor_copies)
Execution Instructions
Step 1: Verify Foundation Directory
- Look for
foundation/in repo root, or../foundation/if in a subdirectory - If not found, error: "Foundation directory not found. Please ensure foundation is installed."
Step 2: Run Setup Script
Execute:
./foundation/scripts/setup_cursor_commands.sh
Or if foundation is in parent directory:
../foundation/scripts/setup_cursor_commands.sh
Step 3: Verify Results
- Check
.cursor/commands/for symlinks to foundation commands (e.g.commit.md,pull.md,push.md) - Repo-specific command files (e.g.
migrate_plans.md) are left unchanged .cursor/rules/is not modified
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.
- 1mo ago First seen · 88 lines · 0 tokens per session scan A 47b21ebb7cdb
setup_commands is a command published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 660 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-09-03.
Other commands, from other repositories
ship-changes
../../.cratis/ai/prompts/ship-changes.prompt.md.
review-pr
../../.cratis/ai/prompts/review-pr.prompt.md.
memory-review
Review contested and stale gitmem memories and propose resolutions.
remember
Save a durable fact or decision to gitmem memory.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.