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.
curl -O https://raw.githubusercontent.com/g-digital-by-Garrigues/GoCertius_MCP/main/.claude/commands/notification-lifecycle.mdgit clone --depth 1 https://github.com/g-digital-by-Garrigues/GoCertius_MCPWrote 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/g-digital-by-garrigues/gocertius_mcp/notification-lifecycle)<a href="https://agentmods.dev/commands/g-digital-by-garrigues/gocertius_mcp/notification-lifecycle"><img src="https://agentmods.dev/badge/commands/g-digital-by-garrigues/gocertius_mcp/notification-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.
<a href="https://agentmods.dev/commands/g-digital-by-garrigues/gocertius_mcp/notification-lifecycle"><img src="https://agentmods.dev/badge/commands/g-digital-by-garrigues/gocertius_mcp/notification-lifecycle.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.00000 | $0.02772 |
| Opus 5 | $0.00000 | $0.01386 |
| Sonnet 5 | $0.00000 | $0.00554 |
| Haiku 4.5 | $0.00000 | $0.00277 |
Grade A, and why
notification-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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- notification-lifecycle — 88% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Certified Notification Lifecycle
Send a certified electronic notification to one or more recipients and obtain a legal certificate for each one.
Notification types
| Type | API value | What recipients can do |
|---|---|---|
| Information only | NO_RESPONSE |
Read only — no reply expected |
| Accept / Reject | ACCEPTED_OR_NOT |
Click Accept or Reject |
| Received / Received + Not Compliant | RECEIVED_AGREE |
Acknowledge receipt and agree or disagree |
Status progression
CREATING → DRAFT → IN_PROCESS → SENT → PARTIALLY_READ / FULLY_READ → PARTIALLY_ANSWERED / FULLY_ANSWERED
The notification stays in DRAFT until explicitly sent via notification_request_send.
The easy way
notification_send does the whole thing in one call — create, add every recipient, send:
notification_send
caseFileId=<cf-id>
subject="Your contract is ready" language=en_GB type=NO_RESPONSE
content="<p>Please review the information below.</p>"
recipients=[ { firstName: "Alice", lastName: "Smith", email: "[email protected]" } ]
It generates every UUID itself. If something fails partway it does not throw away what it built:
the result carries notificationRequestId together with recipientsAdded, recipientsFailed and
sent, so you can finish with the granular tools below.
Attaching files is a different tool — notification_send_with_attachments — because attachments
must go on before recipients. See the notification-attachments skill.
The manual flow
- Create the notification request (stays DRAFT)
notification_request_createwith a generated UUIDid,caseFileId,type,subject,content,language- IMPORTANT —
contentmust be valid HTML. Plain text without HTML tags will not render on the recipient landing page. Supported tags only:<p>,<strong>,<em>,<ul><li>,<ol><li>. No other HTML tags or CSS. Avoid special typographic characters (em dashes, smart quotes) insubject; use standard ASCII equivalents instead. - Optional defaults for every recipient:
otpByDefault,sendWaUrlByDefault,sendSmsUrlByDefault
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.
- 3d ago Changed · +92 lines 821247880956
- 10d ago First seen · 94 lines · 0 tokens per session scan A 906d025732c7
notification-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 2,772 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.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.