GoCertius_MCP: Command for Claude Code

.claude/commands/chat-lifecycle.md

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

A procedure for creating a Telegram chat session in GoCertius and producing a tamper-evident certificate of the conversation. It covers finding the user's personal case file, creating the chat and waiting for its invitation link.

In plain words
What is it for?
Starting a certified Telegram conversation, obtaining its invitation URL, and preserving proof that the chat was not altered.
Why use it?
It prevents mistakes in the required GoCertius setup sequence and helps ensure the conversation can be certified correctly.

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/chat-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 chat-lifecycle

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/g-digital-by-garrigues/gocertius_mcp/chat-lifecycle"><img src="https://agentmods.dev/badge/commands/g-digital-by-garrigues/gocertius_mcp/chat-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,079 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.01079
Opus 5 $0.00000 $0.00540
Sonnet 5 $0.00000 $0.00216
Haiku 4.5 $0.00000 $0.00108

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

Security

Grade A, and why

chat-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/chat-lifecycle.md · 73 lines

How it starts

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

Certified Chat Lifecycle

Create a Telegram-based certified chat session and generate a tamper-evident certificate of the conversation.

Key constraint

Chats can only be created in the user's personal case file — the case file created automatically when the GoCertius account was opened. Creating a chat in any other case file is not supported by the platform even if the API accepts the call. Use session_infocase_file_list to find the personal case file (typically the oldest one, owned by the user).

Flow

  1. Find the personal case file

    • session_info → get userId
    • case_file_list with userId → find the personal case file (oldest createdAt, owned by the user)
    • Note its id and code
  2. Create the chat

    • chat_create with a generated UUID id, caseFileId, title, service: "Telegram", language
    • Optional: serviceTitle (shown in Telegram) and serviceDescription
    • The chat starts in creating status; it transitions to active once the Telegram bot is registered
  3. Get the invitation URL

    • First call chat_get and wait until the chat is no longer creating and registeredAt is present. Calling too early can return Chat not found even though chat_create accepted the request.
    • chat_invitation_url with caseFileId and chatId
    • Returns { invitationUrl: "https://t.me/+..." } — share this link with all participants
    • Participants join the Telegram group; the GoCertius bot records all messages
  4. Participants chat

    • All messages sent in the Telegram group are captured by the GoCertius bot
    • Note: chatMessagesFrom for the certificate must be after the chat's registeredAt timestamp (visible via chat_get)
    • createdAt is not a valid substitute for registeredAt; if registeredAt is missing, wait or ask the user to join/register the chat through the invitation flow before creating a certificate.
  5. Create the certificate

    • chat_certificate_create with a generated UUID id, caseFileId, chatId, name, language
    • chatMessagesFrom: ISO datetime — must be strictly after the chat's registeredAt (use chat_get to confirm; setting it to exactly registeredAt or before causes validation error)
    • chatMessagesTo: ISO datetime — can be now or any future point
    • The certificate is generated asynchronously but typically certifies within seconds

Read the full file on GitHub · 73 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 · 73 lines · 0 tokens per session scan A 33f45a7bc0dd

Subscribe to this mod's changes

chat-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,079 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.