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 curiositech/windags-skills --skill dag-convergence-monitorgit clone --depth 1 https://github.com/curiositech/windags-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/curiositech/windags-skills/dag-convergence-monitor)<a href="https://agentmods.dev/skills/curiositech/windags-skills/dag-convergence-monitor"><img src="https://agentmods.dev/badge/skills/curiositech/windags-skills/dag-convergence-monitor/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/curiositech/windags-skills/dag-convergence-monitor"><img src="https://agentmods.dev/badge/skills/curiositech/windags-skills/dag-convergence-monitor.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.00078 | $0.01968 |
| Opus 5 | $0.00039 | $0.00984 |
| Sonnet 5 | $0.00016 | $0.00394 |
| Haiku 4.5 | $0.00008 | $0.00197 |
Grade A, and why
dag-convergence-monitor 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 9d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago First seen · 173 lines · 78 tokens per session scan A 2d605dcb47a9
dag-convergence-monitor is a skill published in the GitHub repository curiositech/windags-skills (10 stars, last pushed 1mo ago), with no licence file. It adds 78 tokens to every session and 1,968 once invoked, about $0.0004 per session on Opus 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-09-03.
Other skills, from other repositories
taskflow
A workflow coordinator for splitting large coding tasks into multiple phases handled by separate agents.
code-review-quality
Conduct context-driven code reviews focusing on quality, testability, and maintainability. Use when reviewing code, providing feedback, or establishing review practices.
wisp-diagnose
Use when a WISP run failed unexpectedly or is stuck — fetches the event timeline for a run, highlights failures, and prints the verify-failed payloads with full output so the user can see exactly why a task failed. Trigger on phrases like "why did the run fail", "diagnose the harness", "what went wrong with the run".
wisp-resume
Use when the user wants to resume a previously paused WISP run (e.g. paused by rate-limit, by /pause, or by an earlier shutdown). Lists resumable runs and resumes a chosen one. Trigger on phrases like "resume my run", "continue the harness", "pick up where we left off".
wisp-inspect
Use when the user wants to inspect the result branch of a completed WISP run — shows files in the result branch, the per-task git log graph, and a brief summary. Trigger on phrases like "what did harness produce", "show the run output", "inspect the result branch".
auto-doc
Drafts a docs/solutions/YYYY-MM-DD- .md entry for a recently completed run, capturing problem/solution/lessons.