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 skills/bodangren/git-workflow/project-migratenpx skills add bodangren/git-workflow --skill project-migrategit clone --depth 1 https://github.com/bodangren/git-workflowWhat 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.00044 | $0.01072 |
| Opus 5 | $0.00022 | $0.00536 |
| Sonnet 5 | $0.00009 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
project-migrate 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.
Project Migrate Skill
Purpose
To intelligently migrate existing projects (brownfield) to the AgenticDev directory structure using a powerful, AI-assisted workflow. This skill goes beyond simple file moving by leveraging the Gemini CLI to analyze document content, ensuring accurate categorization and the generation of rich, meaningful metadata. It provides a safe, guided migration with discovery, analysis, backup, and validation phases to ensure zero data loss and high-quality results.
When to Use
Use this skill in the following situations:
- Adding AgenticDev to an existing project with established documentation.
- Migrating docs from an ad-hoc structure to AgenticDev conventions.
- When you want to automatically and intelligently categorize and add metadata to existing documents.
- To ensure a safe migration with backups and rollback capabilities.
Prerequisites
- Project with existing documentation (
docs/,documentation/,wiki/, or markdown files). - Git repository initialized.
- Write permissions to the project directory.
geminiCLI tool installed and authenticated.doc-indexerskill available for final compliance checking.
Workflow
The skill guides you through a series of phases with interactive approval.
Step 1: Run the Migration Script
Execute with one of three modes:
Interactive (default) - Review and approve each phase:
bash scripts/project-migrate.sh
Dry-run - Preview the plan without making any changes:
bash scripts/project-migrate.sh --dry-run
Auto-approve - Skip prompts for automation (useful for CI/CD):
bash scripts/project-migrate.sh --auto-approve
Step 2: Review Each Phase
Phase 1 & 2 - AI-Powered Discovery and Analysis:
The script scans for all markdown files. For each file, it calls the Gemini CLI to analyze the document's content, not just its filename. This results in a much more accurate categorization of files into types like spec, proposal, adr, etc. The output is a detailed plan mapping each file to its new, correct location in the AgenticDev structure.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 44 tokens per session scan A 4bdc7448b04b
project-migrate is a skill published in the GitHub repository bodangren/git-workflow (11 stars, last pushed 9mo ago), licensed MIT. It adds 44 tokens to every session and 1,072 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…