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 agentmods add skills/ayeshakhalid192007-dev/graph-engineering-crash-course/gate-task-completionnpx skills add ayeshakhalid192007-dev/graph-engineering-crash-course --skill gate-task-completiongit clone --depth 1 https://github.com/ayeshakhalid192007-dev/graph-engineering-crash-courseWrote 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/ayeshakhalid192007-dev/graph-engineering-crash-course/gate-task-completion)<a href="https://agentmods.dev/skills/ayeshakhalid192007-dev/graph-engineering-crash-course/gate-task-completion"><img src="https://agentmods.dev/badge/skills/ayeshakhalid192007-dev/graph-engineering-crash-course/gate-task-completion.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.00883 |
| Opus 5 | $0.00025 | $0.00441 |
| Sonnet 5 | $0.00010 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
gate-task-completion 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 4d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gate-task-completion
Reads a loop's proposed "done" signal for a task and the checker's run log, and decides whether the task's own checker entry actually exists — passing the loop through only when it does, and blocking with the specific missing check named when it doesn't.
Instructions
You are a Claude Code skill implementing the early-victory-guard
pattern. Follow these steps in order:
- Read the loop's proposed "done" signal for the task, noting the task's own id exactly as the loop states it — this id is what you'll match the checker log against, not the ticket's subject matter or the plausibility of the resolution note.
- Read the checker's run log. Default to the tickets and log in
this kit's
README.mdunless the user gives you a different set. - Search the run log for an entry whose task id exactly matches the proposed "done" signal's task id. A near match — the right subject matter, the right loop, even the right day — does not count. Only an entry keyed to the exact task id counts as coverage.
- If no matching entry exists at all, block. State plainly that the checker never ran against this task, and name the task id that's missing coverage. Do not let a well-written resolution note substitute for the missing run.
- If a matching entry exists but is keyed to a different task id that merely looks similar (a typo, an adjacent ticket number, a logging mixup), treat this the same as no entry — block, and name the mismatch specifically: what task id the loop claimed versus what task id the log actually shows.
- If a matching entry exists for the exact task id, pass the loop through. The guard's job is only to confirm the checker ran against this task at least once — it does not re-run the checker itself and does not second-guess a pass or fail the checker already recorded.
- Report one outcome per task:
PASS(with the matching log entry cited) orBLOCKED(with the specific missing or mismatched task id named). Never report a task without one of these two outcomes.
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.
- 4d ago First seen · 83 lines · 50 tokens per session scan A ec35eaa789c4
gate-task-completion is a skill published in the GitHub repository ayeshakhalid192007-dev/graph-engineering-crash-course (5 stars, last pushed 9d ago), licensed MIT. It adds 50 tokens to every session and 883 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.