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 masteranime/n8n-claude-skills --skill mysql-checkpointinggit clone --depth 1 https://github.com/masteranime/n8n-claude-skillsWrote 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/masteranime/n8n-claude-skills/mysql-checkpointing)<a href="https://agentmods.dev/skills/masteranime/n8n-claude-skills/mysql-checkpointing"><img src="https://agentmods.dev/badge/skills/masteranime/n8n-claude-skills/mysql-checkpointing/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/masteranime/n8n-claude-skills/mysql-checkpointing"><img src="https://agentmods.dev/badge/skills/masteranime/n8n-claude-skills/mysql-checkpointing.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.00137 | $0.01657 |
| Opus 5.5 | $0.00055 | $0.00663 |
| Sonnet 5.5 | $0.00027 | $0.00331 |
| Haiku 4.5 | $0.00014 | $0.00166 |
Grade A, and why
mysql-checkpointing 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 1mo 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MySQL Checkpointing for n8n
Idempotency is not optional. Any workflow that can be re-run must produce identical results on the second run. MySQL (or Postgres — patterns are identical) is the pragmatic way.
The three checkpoint tables every pipeline needs
1. processed_items — did we already handle this?
CREATE TABLE processed_items (
item_key VARCHAR(255) PRIMARY KEY, -- natural ID (webhook event_id, order_id, etc.)
workflow_name VARCHAR(100) NOT NULL,
processed_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
status VARCHAR(20) NOT NULL, -- 'success' | 'failed' | 'skipped'
payload_hash VARCHAR(64), -- SHA256 of payload, detects payload changes
INDEX idx_workflow_status (workflow_name, status),
INDEX idx_processed_at (processed_at)
);
Check THIS FIRST in every workflow. Before any side-effect (email, charge, API call), SELECT item_key FROM processed_items WHERE item_key = ?. If it exists, exit.
2. failed_jobs — dead letter queue
CREATE TABLE failed_jobs (
id BIGINT AUTO_INCREMENT PRIMARY KEY,
workflow_name VARCHAR(100) NOT NULL,
item_key VARCHAR(255),
payload JSON,
error_message TEXT,
error_node VARCHAR(100), -- which n8n node failed
retry_count INT DEFAULT 0,
failed_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
INDEX idx_workflow_retry (workflow_name, retry_count)
);
Every error branch writes here. A retry workflow runs on schedule, picks up retry_count < 3, attempts reprocessing, bumps counter.
3. batch_runs — resumability
CREATE TABLE batch_runs (
id BIGINT AUTO_INCREMENT PRIMARY KEY,
workflow_name VARCHAR(100),
last_cursor VARCHAR(255), -- last ID / timestamp processed
items_processed INT DEFAULT 0,
status VARCHAR(20), -- 'running' | 'complete' | 'failed'
started_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
completed_at TIMESTAMP NULL
);
For batch jobs (scraping, enrichment, imports): persist the cursor after each chunk. On restart, resume from last_cursor instead of starting over.
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.
- 1mo ago First seen · 162 lines · 137 tokens per session scan A c9de339da089
mysql-checkpointing is a skill published in the GitHub repository masteranime/n8n-claude-skills (34 stars, last pushed 6mo ago), licensed MIT. It adds 137 tokens to every session and 1,657 once invoked, about $0.0005 per session on Opus 5.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
moai-platform-database-cloud
Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.
dev-supabase
Backend development with Supabase. Trigger when the user wants to configure auth, the database, or Supabase storage.
ops-database
Database schema design. Trigger when the user wants to create tables, migrations, or optimize queries.
sql-code-review
Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimisation prompt for…
sql-optimisation
Universal SQL performance optimisation assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Provides execution plan analysis, pagination optimisation, batch operations, and performance monitoring guidance.
snowflake-semanticview
Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup.