Borrowing it
Nothing to install: this file belongs to markmhendrickson/ateles. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/markmhendrickson/ateles/main/.claude/skills/setup-cursor-copies/SKILL.mdgit clone --depth 1 https://github.com/markmhendrickson/atelesWrote 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/ateles/setup-cursor-copies)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/setup-cursor-copies"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/setup-cursor-copies.svg" alt="Measured on agentmods" 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.00021 | $0.02212 |
| Opus 5 | $0.00010 | $0.01106 |
| Sonnet 5 | $0.00004 | $0.00442 |
| Haiku 4.5 | $0.00002 | $0.00221 |
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 3d 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.
This is a copy
92% identical to setup-cursor-copies — 29 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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/scripts/setup_cursor_copies.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
When foundation is a symlink or copy (this command uses copy mode):
- Creates independent file copies
- Uses original filenames (no prefix)
- Does NOT update automatically when foundation changes
- Can be customized per repository
- Must re-run script to get foundation updates
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.
- 3d ago First seen · 236 lines · 21 tokens per session scan A 19749a255a9c
setup-cursor-copies is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 2,212 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to setup-cursor-copies, differing in 29 lines, and is treated as a copy.
Other skills, from other repositories
continue
Autonomous work — find and execute ready tasks.
pr
A command for managing pull requests on GitHub or Bitbucket Server. A pull request is a request for other developers to review and merge changes into a project branch.
git-workflow
When the user asks you to perform git operations, create branches, open PRs, manage releases, or resolve conflicts, follow this guide. These are the procedural patterns you should apply consistently.
vcs_collaboration
Experts in asynchronous Git/GitHub collaborative development flow.
release-prep
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.
massgen-release-documenter
Guide for following MassGen's release documentation workflow. This skill should be used when preparing release documentation, updating changelogs, writing case studies, or maintaining project documentation across releases.