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/commands/marcel-bich/marcel-bich-claude-marketplace/project)<a href="https://agentmods.dev/commands/marcel-bich/marcel-bich-claude-marketplace/project"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/project/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/commands/marcel-bich/marcel-bich-claude-marketplace/project"><img src="https://agentmods.dev/badge/commands/marcel-bich/marcel-bich-claude-marketplace/project.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.00021 | $0.00649 |
| Opus 5 | $0.00010 | $0.00324 |
| Sonnet 5 | $0.00004 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
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 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Credo Project Target
credo has two layers. The AUTONOMY layer (keep-alive flags) is global to your user
and is never changed here. This command only sets the PROJECT layer: which repo's
.credo/, config, and items credo operates on.
Why this exists: when your shell cwd is a launch hub (a directory you start other repos from) rather than the repo you are actually working on, credo would otherwise resolve its project layer to the wrong place. Pin the real target instead.
With an argument (set the pin)
The user gave a path in $ARGUMENTS.
- Pin it for this session:
The script validates that the path is an existing directory and keys the pin by the current session_id. If it errors (path missing, no session_id), report the message verbatim and stop - do not guess a path."${CLAUDE_PLUGIN_ROOT}/hooks/session-project-set.sh" "$ARGUMENTS" - Confirm the resolved target:
"${CLAUDE_PLUGIN_ROOT}/scripts/credo-config.sh" resolve-project - Confirm briefly: credo now targets
<resolved .credo dir>for this session.
Without an argument (show the current target)
- Resolve the current target and capture the exit code:
"${CLAUDE_PLUGIN_ROOT}/scripts/credo-config.sh" resolve-project; echo "rc=$?" - Check whether the cwd is a hub:
"${CLAUDE_PLUGIN_ROOT}/scripts/credo-config.sh" is-hub - Report:
- exit 0: credo targets the printed
.credodirectory. - exit 4: no target resolved - the cwd is a hub (
is-hub= true) or has no credo project yet. Tell the user to pin a repo with/credo:project <path>or setCREDO_DIR, then retry whatever needed the target.
- exit 0: credo targets the printed
- If a target resolved (exit 0), also show whether it carries per-repo special rules:
Report"${CLAUDE_PLUGIN_ROOT}/scripts/credo-config.sh" rulesRULES.md: present/RULES.md: noneaccordingly, and note that the user can set per-repo rules any time by asking (for example "set a credo rule here that ..."), which the credorulesskill captures into.credo/RULES.md.
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 · 62 lines · 21 tokens per session scan A 70b7abc6eaa9
project is a command published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (13 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 649 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-30.
Other commands, from other repositories
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
update-docs
Scan for recently modified files and update corresponding documentation.
handoff
Create a handoff document for seamless session continuity.
gws-tasks
List, create, complete, and manage Google Tasks.
gws-standup
Generate a standup report combining today's calendar and tasks.