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 Abhigyan-Shekhar/Waggle-mcp --skill waggle-checkpointgit clone --depth 1 https://github.com/Abhigyan-Shekhar/Waggle-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/skills/abhigyan-shekhar/waggle-mcp/waggle-checkpoint)<a href="https://agentmods.dev/skills/abhigyan-shekhar/waggle-mcp/waggle-checkpoint"><img src="https://agentmods.dev/badge/skills/abhigyan-shekhar/waggle-mcp/waggle-checkpoint/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/abhigyan-shekhar/waggle-mcp/waggle-checkpoint"><img src="https://agentmods.dev/badge/skills/abhigyan-shekhar/waggle-mcp/waggle-checkpoint.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.00032 | $0.00248 |
| Opus 5 | $0.00016 | $0.00124 |
| Sonnet 5 | $0.00006 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
waggle-checkpoint 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.
This is a copy
100% identical to waggle-checkpoint — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Checkpoint durable outcomes
- Review the current task and select only durable outcomes: decisions and rationale, verified fixes and causes, stable constraints, failed approaches worth avoiding, measured results, unresolved problems, and concrete next steps.
- Exclude greetings, raw command logs, speculative thoughts, secrets, duplicate facts, and details easily recovered from the current code unless their historical meaning matters.
- Determine the stable project scope: prefer the credential-free Git remote identity, otherwise the canonical absolute Git root or workspace path.
- Draft a compact checkpoint summary. Call
observe_conversationwith the user's checkpoint request asuser_message, the summary asassistant_response, and the stableproject,agent_id: "codex", and current session identifier when available. - Report what categories were checkpointed and any non-fatal extraction errors. If there is nothing durable, say so and skip the write.
This is the Codex skill equivalent of /waggle-checkpoint; invoke it as $waggle-checkpoint.
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 · 15 lines · 32 tokens per session scan A eb812d9ce210
waggle-checkpoint is a skill published in the GitHub repository Abhigyan-Shekhar/Waggle-mcp (40 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 248 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to waggle-checkpoint, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
graph-ask
Ask any natural language question about the memory graph. You generate Cypher directly and execute it. Use when the user has a complex or ad-hoc question that the standard graph tools don't cover.
ingest-audio
Transcribe a local audio or video file using Whisper and ingest it into the memory graph. Use when the user has a local MP3, WAV, M4A, MP4, or similar audio/video file they want to add to their knowledge graph.
ingest
Ingest a file or URL into the memory graph. Handles local files (text, PDF, DOCX, XLSX, images, etc.) and URLs (web pages, YouTube, Wikipedia, RSS). Use when the user wants to add any document or web content to their knowledge graph.
graph-backup
Export the memory graph to a timestamped JSONL backup file. Use before risky operations or on demand.
graph-briefing
Generate a session briefing from the memory graph — recent changes, unresolved contradictions, relevant context for the current project. Use at the start of a session to catch up, or when switching projects.
graph-dream
Manually run the graph memory dream process to extract entities from recent conversations and ingested documents. Use when the user wants to update the graph now rather than waiting for the scheduled run.