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 skills add Marcel-Bich/marcel-bich-claude-marketplace --skill cross-cutting-checklist-generatorgit clone --depth 1 https://github.com/Marcel-Bich/marcel-bich-claude-marketplaceWrote 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/cross-cutting-checklist-generator)<a href="https://agentmods.dev/skills/marcel-bich/marcel-bich-claude-marketplace/cross-cutting-checklist-generator"><img src="https://agentmods.dev/badge/skills/marcel-bich/marcel-bich-claude-marketplace/cross-cutting-checklist-generator/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/cross-cutting-checklist-generator"><img src="https://agentmods.dev/badge/skills/marcel-bich/marcel-bich-claude-marketplace/cross-cutting-checklist-generator.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.00094 | $0.00916 |
| Opus 5 | $0.00047 | $0.00458 |
| Sonnet 5 | $0.00019 | $0.00183 |
| Haiku 4.5 | $0.00009 | $0.00092 |
Grade A, and why
cross-cutting-checklist-generator 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cross-cutting-checklist-generator
Keep concerns that are spread across many spots from being updated in only some of them. When a concern appears in enough scattered places, generate a project-local checklist of every spot; then consult and update that checklist automatically on later changes. Fully autonomous - the user does nothing.
The problem this solves
Some concerns live in many places at once: a config key referenced from several modules, an enum handled in multiple switches, a translation across locale files, a feature flag checked in several components, an endpoint listed in client plus docs. Add a new case and it is easy to update three spots and miss the fourth. These checklists make the full set of spots explicit so nothing is left half-done.
When this fires
- You add or modify something and notice the SAME concern already exists in several other places (a scattered, cross-cutting concern).
- You edit a spot that a checklist already covers (consult and update it).
- You are about to report work complete on a concern that has a checklist (verify completeness against it).
This fires inside subagents too: a subagent editing a scattered concern consults and maintains the checklist just as the main agent would.
Where checklists live
Project-local files under .credo/checklists/ (the credo per-project namespace from
scripts/credo-init.sh), one file per concern, named after the concern (ASCII, for
example .credo/checklists/config-keys.md). Write atomically per the credo persistence
convention. .credo/** is git-excluded; these are working artifacts, not committed.
Auto-create (default threshold ~3 scattered spots)
When you find a concern touched in roughly three or more separate spots and no checklist exists yet, create one automatically. The threshold is a soft default (about 3) and a matter of judgment, not a hard rule - create earlier if the concern is clearly cross-cutting and error-prone, and do not manufacture a checklist for something that genuinely lives in one place. If the config exposes a threshold value, honor it; otherwise use ~3.
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 · 85 lines · 94 tokens per session scan A 275d5b83bc92
cross-cutting-checklist-generator is a skill published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (13 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 916 once invoked, about $0.0005 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.
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.
battle-card-builder
Competitive battle card creation for sales teams combining competitive intelligence, sales enablement, and document formatting. Use when building battle cards, competitive analysis decks, or win/loss analysis materials.