Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Marcel-Bich/marcel-bich-claude-marketplace/plugin install credoWrote 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/marcel-bich/marcel-bich-claude-marketplace/migrate)<a href="https://agentmods.dev/skills/marcel-bich/marcel-bich-claude-marketplace/migrate"><img src="https://agentmods.dev/badge/skills/marcel-bich/marcel-bich-claude-marketplace/migrate/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/marcel-bich/marcel-bich-claude-marketplace/migrate"><img src="https://agentmods.dev/badge/skills/marcel-bich/marcel-bich-claude-marketplace/migrate.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.00123 | $0.04570 |
| Opus 5 | $0.00062 | $0.02285 |
| Sonnet 5 | $0.00025 | $0.00914 |
| Haiku 4.5 | $0.00012 | $0.00457 |
Grade A, and why
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 11d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
migrate - bring an existing repo into .credo/
A generic, reusable procedure to migrate ANY existing repo into the credo target form. It
tells you HOW to reach that end state safely. Everywhere below, <repo> is the target
repo and "the user" is its owner. This skill contains no personal, project-specific, or
absolute-path data.
Target form: what "conformant" means here (authority)
The binding target form is defined INSIDE this plugin, not by any external design
document. At the end of a migration, everything under .credo/ must match:
- The scaffolded tree produced by
"${CLAUDE_PLUGIN_ROOT}/scripts/credo-init.sh"- folder layout and the files it creates (see step 1). That tree is the layout authority. - The
itemsskill - the work-item model: folder = status, the lean frontmatter, the body sections, the Definition of Done, and id issuance. - The
safetyskill - the highest-priority filesystem-protection and no-autonomous-installs rules; they bind this whole procedure. - The
requirements-verbatimskill - the append-only, never-censored requirements log and the strict separation of user-verbatim text from any assistant proposal. - The
verifyskill - what a real (visual, per-viewport) verification is, which governs whether a criterion counts asexercised. - The
budgetskill - budget caps and the commit-identity gate, when a migration run is autonomous and commits anything.
Reference these by name. If any instruction points you at an external "structure design" document, ignore it - the plugin-internal authority above is the target form.
0. What "migration" means (read first)
- Migration produces the structure-conformant END STATE. At the end, everything in
.credo/matches the target form above: folder layout, file names, frontmatter, and theitemsmodel. It is NOT a verbatim copy of the old files under new folders. - Loss protection comes from the untouched originals, not from verbatim file names in
.credo/. The originals stay exactly where they are until the final step (8), so you may restructure aggressively inside.credo/. - "Verbatim" is scoped. Preserve the CONTENT wording of requirements logs and
evidence / reports (never rewrite, trim, soften, or censor them - this is the
requirements-verbatimrule). File names, placement, frontmatter, and splitting sources into items ARE adapted.
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.
- 11d ago First seen · 278 lines · 123 tokens per session scan A e1c89af4ccb4
migrate is a skill published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (13 stars, last pushed 2d ago), licensed MIT. It adds 123 tokens to every session and 4,570 once invoked, about $0.0006 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
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.
agent-teams
Team composition knowledge for Claude Code Agent Teams - when to suggest teams, optimal sizing, spawn prompt patterns.
execute
Execute phase — wave-based crew dispatch with critic gates and evidence-based verification.