A procedure for bringing an existing project into the conventions of a Copier template, a system that generates and updates project files from a template. It first detects whether the project is already template-based or needs a full structural port.

Use it to update a project created with Copier or port a manually organized data-science project into the copier-data-science structure.

It removes uncertainty about how an older or partly structured project should match the template. It also preserves existing work while reviewing template updates or reorganizing legacy files.

fix-project — Skill by stellarshenson

Install

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.

agentmods

npx agentmods add skills/stellarshenson/claude-code-plugins/fix-project

Any agent

npx skills add stellarshenson/claude-code-plugins --skill fix-project

Clone the repo

git clone --depth 1 https://github.com/stellarshenson/claude-code-plugins

Made for: Claude Code, Codex.

Or install datascience, the plugin that ships this one along with the rest of its 20 skills, 15 commands.

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 908 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00019	$0.00908
Opus 5	$0.00010	$0.00454
Sonnet 5	$0.00004	$0.00182
Haiku 4.5	$0.00002	$0.00091

Measured 3d ago against content hash 3d30ccea473c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fix-project 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.

plugins/datascience/skills/fix-project/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix Project Structure

Port an existing data science project to the copier-data-science template standards, or update an already-templated project to the latest version.

Step 1: Detect project state

Check the project root for:

.copier-answers.yml -> project was created with copier (can update)
Makefile with known targets -> partial copier structure
Neither -> legacy/manual project (needs full port)

Report the detected state and ASK user to confirm.

Mode A: Update existing copier project

If .copier-answers.yml exists:

copier update --trust

This pulls the latest template changes while preserving user modifications. Review the diff and resolve any conflicts.

If copier is not installed: pip install copier or uv tool install copier.

Mode B: Port legacy project to copier

If no .copier-answers.yml:

Audit current structure:
- List all directories and their contents
- Identify: data directories, notebooks, source modules, model artifacts, configs
- Map existing structure to copier-data-science conventions
ASK user:
- Project name (for copier)
- Author name and email
- What to preserve vs what to reorganize
- Any directories that should NOT be moved

Create copier scaffold alongside:

copier copy https://github.com/stellarshenson/copier-data-science .copier-temp

Port existing files:
- Move *.py notebooks to notebooks/ (if not already there)
- Move data files to data/{raw,processed,interim}/ based on content
- Move model artifacts to models/
- Move source modules to src/<project_name>/
- Merge Makefiles (keep existing targets, add missing copier targets)
- Merge .gitignore (union of both)
- Merge pyproject.toml / setup.py (keep deps, adopt structure)
Install copier answers:
- Move .copier-answers.yml from temp scaffold to project root
- Remove temp scaffold
- Now copier update works for future template updates

Read the full file on GitHub · 96 lines

Changes

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 · 96 lines · 19 tokens per session scan A 3d30ccea473c

Subscribe to this mod's changes

fix-project is a skill published in the GitHub repository stellarshenson/claude-code-plugins (3 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 908 once invoked, about $0.0001 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.

Project management

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens