Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. 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/rakovi4/continue-framework/main/.claude/skills/task/SKILL.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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/rakovi4/continue-framework/task)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/task"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/task/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/rakovi4/continue-framework/task"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.00646 |
| Opus 5.5 | $0.00016 | $0.00258 |
| Sonnet 5.5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
task 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/task - Create Task
Input
- type (optional):
behavior-change,bugfix,refactor,infra,general, orqa - title (optional): short title of two to five words
Workflow
- List every directory under
ProductSpecification/tasks/andProductSpecification/tasks/done/. Extract and show every leading integer; the next global task number is the maximum plus one, or 1 when none exist. Before creation, verify no folder in either location starts with that number. - Parse the canonical type and title. If either is missing, ask for it.
- Create
ProductSpecification/tasks/{N}-{type}-{slug}/, with a lowercase, hyphenated slug of at most five words. - Gather the type-specific spec in two or three rounds:
- behavior-change: problem, current and expected observable behavior, constraints, and likely key files; do not pre-plan TDD steps.
- bugfix: symptoms, observed versus expected behavior, environment, frequency, captured errors, and reproduction; do not ask for a cause, solution, affected layers, or key files.
- refactor: structural problem, behavior-preserving outcome, constraints, and likely key files; do not pre-plan implementation steps.
- infra: problem, intended infrastructure-as-code outcome, constraints, likely files, and bounded direct work units. Never plan manual remote changes.
- general: problem, intended outcome, constraints, likely files, and bounded direct work units.
- qa: why and when to run the checklist, target environment, session duration, and numbered one-line cases; omit affected layers and key files.
- Generate
spec.mdandprogress.mdfrom.claude/templates/task/creation-formats.md:behavior-change:designthensteps discovery; discovery inserts TDD.bugfix: root-cause-first discovery; discovery inserts TDD.refactor: design and discovery insert direct behavior-preserving steps.infraandgeneral:design, then one direct step per Work item.qa:design, then one manual checkbox per case.
- Show both files for review, then commit them as
task: spec (Task {N}, {title}).
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 · 53 lines · 40 tokens per session scan A 307ba3db5414
task is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 40 tokens to every session and 646 once invoked, about $0.0002 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
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.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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,"…
remove
Remove a deployed framework or addon from the current workspace.