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/role-plan)<a href="https://agentmods.dev/skills/marcel-bich/marcel-bich-claude-marketplace/role-plan"><img src="https://agentmods.dev/badge/skills/marcel-bich/marcel-bich-claude-marketplace/role-plan/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/role-plan"><img src="https://agentmods.dev/badge/skills/marcel-bich/marcel-bich-claude-marketplace/role-plan.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.00199 | $0.00743 |
| Opus 5 | $0.00100 | $0.00371 |
| Sonnet 5 | $0.00040 | $0.00149 |
| Haiku 4.5 | $0.00020 | $0.00074 |
Grade A, and why
role-plan 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 12d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Role: plan / clarify
Set this session's credo ROLE to plan / clarify. This is a guiding default owner of
clarifying items in 1_clarify/, WITHOUT commits or push. Committing and pushing are the
task/build role's job, so a single index owner avoids a race on .git/index.lock.
A role is orthogonal to the session mode (active | passive | autonomous): it can coexist with any mode. It is a guiding default, NOT a fixed constraint - on the user's wish you may still do mixed work, and an explicit user instruction always overrides the role.
When to use
- The user runs
/credo:role-plan(the explicit, deterministic, guaranteed path). - The user assigns you this role in passing (best-effort, casual path) - for example "you are now the plan/clarify agent", "you clarify the items", "take over the clarifying", "act as the plan agent", "uebernimm das Klaeren", "du bist der plan/clarify agent".
Do NOT trigger on general discussion about roles, on explanations, or on questions such as "what does the plan agent do" - those are not an assignment.
What it does
Write the persistent, per-session role marker. It is keyed by session_id under the
session-roles dir and re-injected on every prompt by role-inject.sh, so it survives context
compaction, new sessions and subagents (stored on disk, not in context):
"${CLAUDE_PLUGIN_ROOT}/hooks/role-set.sh" plan
Sandbox pre-work
For WRITING clarify pre-work that needs no product decision but evidence - a measurement, a
mockup, a feasibility proof - use the sandbox skill. It builds under .credo/sandbox-tmp/
(no production code, no commit); an accepted artifact is promoted via /credo:sandbox-promote,
which the task / build role commits.
Confirm
Confirm in one short sentence, for example:
Role set to plan/clarify - I am the default owner of clarifying items in
1_clarify/, without commits or push (the task/build role owns those). This is persistent and compact-safe (re-injected each turn); it is a guiding default you can override, and/credo:role-clearremoves it.
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.
- 12d ago First seen · 61 lines · 199 tokens per session scan A aca7635f91e0
role-plan is a skill published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (13 stars, last pushed today), licensed MIT. It adds 199 tokens to every session and 743 once invoked, about $0.0010 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
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
ios-development
Comprehensive guide for building native Apple platform applications.
ai-policy-generator
AI governance policy creation for nonprofits and enterprises with frameworks, risk assessment, ethical guidelines, and compliance templates. Use when drafting AI usage policies, responsible AI frameworks, or organizational AI governance documents.