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/rakovi4/continue-framework/tasknpx skills add rakovi4/continue-framework --skill taskgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWhat 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.00040 | $0.00646 |
| Opus 5 | $0.00020 | $0.00323 |
| Sonnet 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 2d 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.
- 2d ago First seen · 53 lines · 40 tokens per session scan A 307ba3db5414
task is a skill published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 646 once invoked, about $0.0002 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-30.
Other skills, from other repositories
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.