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/continue/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/continue)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/continue"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/continue/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/continue"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/continue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 14 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 31 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- medium Agent Snooping · line 69 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 131 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00029 | $0.05245 |
| Opus 5.5 | $0.00012 | $0.02098 |
| Sonnet 5.5 | $0.00006 | $0.01049 |
| Haiku 4.5 | $0.00003 | $0.00524 |
Grade A, and why
continue 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 29d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/continue - Resume Development
Workflow
- Identify work item from argument
- Backlog promotion -- if the story row is in the Backlog table in
ProductSpecification/stories.md, move it to In Progress before proceeding - Read progress file, bootstrap if missing (stories only —
.claude/templates/workflow/bootstrapping.md). Missing means both locations came back empty — resolveProductSpecification/stories/NN-story-name/andProductSpecification/stories/done/NN-story-name/before the bootstrap may fire (.claude/rules/workflow.md, "Resolving a story folder"); a hit in either is the story, so read itsprogress.mdand bootstrap nothing. What an unchecked bootstrap does to an already-shipped story is in the template's "Precondition: the story genuinely has no folder" For an existing task, normalize legacyType: bugtobugfixandType: refactoringtorefactorin memory; do not rewrite its type or folder merely to migrate terminology. - Select execution mode -- for an active story with completed specification, load
.claude/templates/workflow/story-stages.mdand reconcilestory-quality-checklist.mdbefore deciding whether implementation remains, even when old scenario checkboxes are all complete. Preserve scenario order; add required quality entries and reopen unsupported completions. Find next step -- run the plan-integrity check (.claude/templates/workflow/plan-integrity-check.md) overprogress.md; on a failed check report it and STOP without dispatching. Otherwise the first[~]or[ ]entry remains the physical cursor; story implementation selects eligible work by the coordinator's current pass, which may reach a later scenario before an earlier scenario's implementation. A task with none archives immediately. - Read relevant context -- for story implementation, scope summaries, referenced work logs, and ADRs to all included scenarios across both tiers as directed by
story-stages.md. Otherwise readcarryover.md(if present), the current scenario's summary, and onlyworklog/records matching the current heading/step or named by its compact pointer. Do not load the directory wholesale./continuenever writes journey files (/handoffis their sole writer). - Load ADR context -- check for
decisions/*-decision.mdfiles in the story directory. If any exist AND the current step or whole-story scope references the ADR (via "see ADR" annotation or matching scenario), read it. ADRs contain architectural decisions, schema changes, edge cases, and implementation guidance that the work unit needs. - Execute -- story implementation runs the whole-story coordinator through all remaining passes in this invocation. Tasks and specification execute one work unit: dispatch sub-skills per tables below. If no named row matches, execute the checkbox intent directly in the main agent.
- Discovery gates -- when the next step is
[ ] adapters-discovery, map usecase ports to adapters (see.claude/guidelines/workflow-detail.md), then insert concrete steps. A TDD task'ssteps discoveryinserts its scoped TDD plan; a refactor task'srefactor (steps discovery)reconciles direct## Workcheckboxes, not merely a companion artifact. - Update records -- create one
worklog/Markdown record for this invocation (maximum 200 lines) and keep routine evidence, notes, coordinator plans, checkpoints, and proposals there. Composite stages update this active record while in flight. Keepprogress.mdto headings, permitted compact tokens, and one-line checkboxes of at most 200 characters: mark completed and advance next. Completed quality entries require a compact work-log pointer; other entries need one only when a later decision consumes that exact record. New finding-driven checkboxes must pass.claude/templates/workflow/finding-admission-test.md; materializing prescribed quality phases is existing work, not a new finding. - Update stories.md -- for stories only, update the phase columns in
ProductSpecification/stories.md(see below) - Behavior commit -- include
progress.md, the invocation's work-log record, andProductSpecification/stories.mdfor stories. Before every progress commit, stage it and run plan-integrity check 8 against its zero-context staged diff; only added lines are checked, so legacy prose is grandfathered. Active stories also run check 9 against staged progress and evidence. Re-home any rejected evidence in the active work-log record and re-stage. For completion, also confirm the staged advance and zero[ ]/[~]entries. Archive only after every required quality phase, including owed refactor, has completed and its evidence is committed. - Refactor -- land any owed
/refactorseparately.
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.
- 1mo ago Changed 2bf21d527353
- 1mo ago Changed · +4 lines ae6ee666758d
- 1mo ago Changed · +3 lines 15b624b42a43
- 1mo ago Changed · +15 lines 7dc6c29b7704
- 1mo ago Changed · -29 lines ad2a28ade2a1
- 1mo ago Changed 72dccde917ab
- 2mo ago First seen · 170 lines · 29 tokens per session scan A a5fd7e98012e
continue is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 29 tokens to every session and 5,245 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.