GoCertius_MCP: Command for Claude Code

.claude/commands/dossier-lifecycle.md

dossier-lifecycle is a command for Claude Code from g-digital-by-Garrigues/GoCertius_MCP. It costs 0 tokens per session (1,132 once invoked), scanned A, original, MIT.

A command workflow for creating certified dossiers: tamper-evident PDF files that collect evidence from a case file.

In plain words
What is it for?
Creating a dossier from one evidence group or selecting evidence across groups, optionally using a template and language settings.
Why use it?
It organizes selected evidence into a document whose contents can show if they were changed after certification.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is g-digital-by-Garrigues/GoCertius_MCP's own configuration. It tells Claude Code how to work on GoCertius_MCP itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything GoCertius_MCP configures →

Reuse

Borrowing it

Nothing to install: this file belongs to g-digital-by-Garrigues/GoCertius_MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/g-digital-by-Garrigues/GoCertius_MCP/main/.claude/commands/dossier-lifecycle.md
Clone the repo
git clone --depth 1 https://github.com/g-digital-by-Garrigues/GoCertius_MCP

Made for: Claude Code.

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.

agentmods badge for dossier-lifecycle

README.md
[![agentmods](https://agentmods.dev/badge/commands/g-digital-by-garrigues/gocertius_mcp/dossier-lifecycle/github.svg)](https://agentmods.dev/commands/g-digital-by-garrigues/gocertius_mcp/dossier-lifecycle)
Your own site
<a href="https://agentmods.dev/commands/g-digital-by-garrigues/gocertius_mcp/dossier-lifecycle"><img src="https://agentmods.dev/badge/commands/g-digital-by-garrigues/gocertius_mcp/dossier-lifecycle/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.

agentmods 80×15 button for dossier-lifecycle

Your own site · 80×15
<a href="https://agentmods.dev/commands/g-digital-by-garrigues/gocertius_mcp/dossier-lifecycle"><img src="https://agentmods.dev/badge/commands/g-digital-by-garrigues/gocertius_mcp/dossier-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,132 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01132
Opus 5 $0.00000 $0.00566
Sonnet 5 $0.00000 $0.00226
Haiku 4.5 $0.00000 $0.00113

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

Security

Grade A, and why

dossier-lifecycle 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 10d 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.

.claude/commands/dossier-lifecycle.md · 94 lines

How it starts

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

Dossier Lifecycle

Create certified dossiers (tamper-evident PDFs) that bundle one or more evidence items from a case file.

Two creation modes

Mode Tool Evidences When to use
Express dossier_group_certify All from ONE evidence group Single group, one step
Full dossier_createdossier_evidence_linkdossier_certify Any subset from any groups Multiple groups or specific evidence selection

Full flow (multi-group)

  1. Select a template (optional)

    • dossier_template_list — returns available templates with their IDs and translations
    • Pass the returned id as dossierTemplateId in dossier_create if you need a specific template
  2. Create a DRAFT dossier

    • dossier_create with a generated UUID id, caseFileId, name, language, validityFrom, validityTo
    • The dossier starts in DRAFT status with 0 evidences
  3. Link evidences

    • dossier_evidence_link with caseFileId, dossierId, caseFileToLinkId (same as caseFileId when evidences are in the same case file), and ids (array of evidence UUIDs)
    • Can be called once with all evidence IDs, or multiple times for different batches
    • Only COMPLETED evidences from sealed groups can be linked
  4. Certify

    • dossier_certify with caseFileId and dossierId
    • Dossier transitions DRAFTCERTIFYINGCERTIFIED
    • Certification is asynchronous; poll dossier_list until status: CERTIFIED
    • Note: dossier_certify has no SSE bridge — always poll regardless of runtime

Express flow (single group)

dossier_group_certify  id=<uuid>  caseFileId=<id>  evidenceGroupId=<group-id>
  name="..."  language=es_ES
  [evidenceIds=["uuid1","uuid2"]]   ← optional: filter specific evidences within the group

The express endpoint creates AND certifies in one call. Do NOT call it in parallel with the same id — the first call creates and certifies immediately, subsequent calls fail.

Example — all evidences across multiple groups

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

  1. 10d ago First seen · 94 lines · 0 tokens per session scan A 7b8db0154fdf

Subscribe to this mod's changes

dossier-lifecycle is a command published in the GitHub repository g-digital-by-Garrigues/GoCertius_MCP (0 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,132 tokens. 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-31.