Borrowing it
Nothing to install: this file belongs to vguleaev/cursor-todo-prompt-kit. 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/vguleaev/cursor-todo-prompt-kit/main/.cursor/skills/ct-check-task-id/SKILL.mdgit clone --depth 1 https://github.com/vguleaev/cursor-todo-prompt-kitWrote 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/vguleaev/cursor-todo-prompt-kit/ct-check-task-id)<a href="https://agentmods.dev/skills/vguleaev/cursor-todo-prompt-kit/ct-check-task-id"><img src="https://agentmods.dev/badge/skills/vguleaev/cursor-todo-prompt-kit/ct-check-task-id/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/vguleaev/cursor-todo-prompt-kit/ct-check-task-id"><img src="https://agentmods.dev/badge/skills/vguleaev/cursor-todo-prompt-kit/ct-check-task-id.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.00017 | $0.00147 |
| Opus 5.5 | $0.00007 | $0.00059 |
| Sonnet 5.5 | $0.00003 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
ct-check-task-id 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 2mo 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.
What it actually says
ct-check-task-id
For the given task ID, check if it is completed.
TODO.md file Rules
- You must check if the
CT-<number>task is completed inTODO.mdfile. - Understand if all acceptance criteria are met for this task.
- You must set task status to
✅ DONEif all acceptance criteria are met. - You must set task acceptance criteria checkboxes to
[x]if it's acceptance criteria is met.
IMPORTANT: IF task ID is not mentioned, you must ask for it.
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.
- 2mo ago First seen · 19 lines · 17 tokens per session scan A b698bea7e84e
ct-check-task-id is a skill published in the GitHub repository vguleaev/cursor-todo-prompt-kit (3 stars, last pushed 8mo ago), licensed MIT. It adds 17 tokens to every session and 147 once invoked, about $0.0001 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-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…