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 skills/markmhendrickson/neotoma/setup-cursor-copiesWrote 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/skills/markmhendrickson/neotoma/setup-cursor-copies)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/setup-cursor-copies"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/setup-cursor-copies/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/skills/markmhendrickson/neotoma/setup-cursor-copies"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/setup-cursor-copies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 6 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 44 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00010 | $0.02255 |
| Opus 5.5 | $0.00004 | $0.00902 |
| Sonnet 5.5 | $0.00002 | $0.00451 |
| Haiku 4.5 | $0.00001 | $0.00226 |
Grade A, and why
setup-cursor-copies 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- setup_cursor_copies — 100% identical, 13 lines differ
- setup-cursor-copies — 92% identical, 29 lines differ
- setup-cursor-copies — 89% identical, 29 lines differ
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: setup-cursor-copies description: Setup foundation cursor rules and commands in .cursor/ (run setup script). triggers:
- setup cursor copies
- sync cursor files
- scripts/setup_claude_instructions.sh
- setup-cursor-copies
Setup Foundation Cursor Copies
Sets up foundation cursor rules and commands in .cursor/. When foundation is a git submodule, creates symlinks (stays in sync with git submodule update). Otherwise creates independent copies.
Command
setup_cursor_copies
or
setup cursor copies
Purpose
This command runs the foundation setup script (foundation/scriptsscripts/setup_claude_instructions.sh.sh) which:
- If foundation is a git submodule: Delegates to
setup_cursor_rules.shand creates symlinks from foundation to.cursor/(single source of truth; updates apply withgit submodule update). - Otherwise: Creates independent copies of foundation rules/commands in
.cursor/. - Uses original filenames (no prefix).
- Removes existing foundation files before creating new ones.
- Preserves any non-foundation files (custom rules/commands).
When run from the foundation repository itself, it also automatically runs the setup script in peer repositories (located at ../*) that include this foundation repo via symlink.
When to Use
- Submodule: Run after
git submodule update(or any setup); symlinks keep.cursor/in sync automatically. - Copy mode (foundation not a submodule): When you want independent copies, need to customize rules, symlinks are not suitable, or you version-control your own copies. Re-run after foundation updates to refresh.
Submodule vs copy behavior
When foundation is a git submodule (this command delegates to setup_cursor_rules):
- Creates symlinks to foundation (single source of truth)
- Updates automatically when foundation changes (
git submodule update) - Cannot customize foundation rules without breaking the link
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 · 241 lines · 10 tokens per session scan A 643d818c051f
setup-cursor-copies is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 2,255 once invoked, about $0.0000 per session on Opus 5.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-30.
Other skills, from other repositories
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
bilibili_search
Search for videos on Bilibili using keyword queries generated from user interests.
bernstein-plan
Create and manage multi-step execution plans in Bernstein. Plans decompose complex goals into stages with dependencies. Use when the user wants to plan a complex feature, break down a large task, or review an execution plan before agents start working.
bernstein-run
Run a verified multi-agent goal with Bernstein. Use when a task is too large for a single agent session: Bernstein decomposes the goal into tasks, spawns CLI coding agents in parallel git worktrees, verifies their output, and merges results. Also use to check run status, costs, and to verify a finished run against its…
taste-explorer
A guided interview skill that asks focused questions to learn what a person likes and dislikes, then saves confirmed preferences as long-term memory.
bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.