A work-tracking system where each task is a Markdown file, and its folder determines whether it is pending, active, or done. A Definition of Done is the required checklist for considering a task complete.

Use it to create, update, move, and track repository work items. It applies when credo is the configured task system; projects using GSD follow GSD's workflow instead.

Using the folder as the single status source avoids conflicting task states in different trackers. It also prevents work from being marked finished before its required conditions are met.

items — Skill for Claude Code by Marcel-Bich

Install

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.

Claude Code

/plugin marketplace add Marcel-Bich/marcel-bich-claude-marketplace

Claude Code

/plugin install credo

Made for: Claude Code.

Or install credo, the plugin that ships this one along with the rest of its 26 skills, 15 commands, 6 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/marcel-bich/marcel-bich-claude-marketplace/items/github.svg)](https://agentmods.dev/skills/marcel-bich/marcel-bich-claude-marketplace/items)

Your own site

<a href="https://agentmods.dev/skills/marcel-bich/marcel-bich-claude-marketplace/items"><img src="https://agentmods.dev/badge/skills/marcel-bich/marcel-bich-claude-marketplace/items/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/marcel-bich/marcel-bich-claude-marketplace/items"><img src="https://agentmods.dev/badge/skills/marcel-bich/marcel-bich-claude-marketplace/items.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00143	$0.08859
Opus 5	$0.00072	$0.04430
Sonnet 5	$0.00029	$0.01772
Haiku 4.5	$0.00014	$0.00886

Measured 11d ago against content hash e85e6558dc61, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

items 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.

plugins/credo/skills/items/SKILL.md · 576 lines

How it starts

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

items - the credo work-item model

A work item is a single Markdown file under .credo/items/. The folder the file lives in is the only source of truth for its status. There is no status field, no marker, no task-tracker entry - an item changes status by physically moving between folders. This is deliberate anti-drift: multiple status sources drift out of sync, one physical location cannot. .credo/items/ IS the task system; do not mirror items into a separate task list. "Do not mirror" does NOT mean "never use the harness task list at all" - it means no FULL items live there; references to items are fine (see "Harness task-list vs .credo items" below).

Task backend. If the task backend is gsd (set in .credo/config as task_backend, or via the CREDO_TASK_BACKEND env override; resolve with credo-config.sh backend), the credo item system is inactive - GSD's phases are the task system for this project. Do NOT create or move .credo/items/; use GSD's workflow instead. This skill applies only when the backend is credo (the default) or none.

Status = folder (the only truth)

The folder tree (created by credo-init) and what each folder means:

.credo/items/
  1_todo/
    1_clarify/     open questions - needs the user, NOT buildable yet
    2_go/          clarified and approved - buildable (go-gate: only 2_go is buildable)
    3_blocked/     GO'd but hard-blocked by another (unbuilt) credo item; auto-returns to 2_go on unblock
  2_done/          Definition of Done met (agent and/or user), gate passed
  3_verified/      human-authorized - human-in-the-loop confirmation (main agent moves here only on explicit user instruction)
  4_archived/      abandoned / deprecated / rejected
  parked/
    hold/          blocked by an EXTERNAL dependency (not another credo item)
    future/        deliberately deferred

Never encode status anywhere else. If you want to know an item's status, look at which folder its file is in - nothing else is authoritative.

Read the full file on GitHub · 576 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.

11d ago First seen · 576 lines · 143 tokens per session scan A e85e6558dc61

Subscribe to this mod's changes

items is a skill published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (13 stars, last pushed yesterday), licensed MIT. It adds 143 tokens to every session and 8,859 once invoked, about $0.0007 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.

Claude Code Project management ai-tools anthropic claude claude-ai claude-code-plugins

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.

travisjneuman/.claude · 47 tokens

event-planner

Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.

travisjneuman/.claude · 37 tokens

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.

travisjneuman/.claude · 47 tokens

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.

travisjneuman/.claude · 49 tokens

agent-teams

Team composition knowledge for Claude Code Agent Teams - when to suggest teams, optimal sizing, spawn prompt patterns.

travisjneuman/.claude · 24 tokens

execute

Execute phase — wave-based crew dispatch with critic gates and evidence-based verification.

fakoli/fakoli-plugins · 16 tokens