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 skills add opencue/cuecards --skill vc-sequential-thinkinggit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/vc-sequential-thinking)<a href="https://agentmods.dev/skills/opencue/cuecards/vc-sequential-thinking"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/vc-sequential-thinking.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.1 | $0.00036 | $0.00685 |
| Opus 5 | $0.00018 | $0.00342 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
vc:sequential-thinking 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 3d 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.
This is a copy
95% identical to vc-sequential-thinking — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sequential Thinking
Structured problem-solving via manageable, reflective thought sequences with dynamic adjustment.
When to Apply
- Complex problem decomposition
- Adaptive planning with revision capability
- Analysis needing course correction
- Problems with unclear/emerging scope
- Multi-step solutions requiring context maintenance
- Hypothesis-driven investigation/debugging
Core Process
1. Start with Loose Estimate
Thought 1/5: [Initial analysis]
Adjust dynamically as understanding evolves.
2. Structure Each Thought
- Build on previous context explicitly
- Address one aspect per thought
- State assumptions, uncertainties, realizations
- Signal what next thought should address
3. Apply Dynamic Adjustment
- Expand: More complexity discovered → increase total
- Contract: Simpler than expected → decrease total
- Revise: New insight invalidates previous → mark revision
- Branch: Multiple approaches → explore alternatives
4. Use Revision When Needed
Thought 5/8 [REVISION of Thought 2]: [Corrected understanding]
- Original: [What was stated]
- Why revised: [New insight]
- Impact: [What changes]
5. Branch for Alternatives
Thought 4/7 [BRANCH A from Thought 2]: [Approach A]
Thought 4/7 [BRANCH B from Thought 2]: [Approach B]
Compare explicitly, converge with decision rationale.
6. Generate & Verify Hypotheses
Thought 6/9 [HYPOTHESIS]: [Proposed solution]
Thought 7/9 [VERIFICATION]: [Test results]
Iterate until hypothesis verified.
7. Complete Only When Ready
Mark final: Thought N/N [FINAL]
Complete when:
- Solution verified
- All critical aspects addressed
- Confidence achieved
- No outstanding uncertainties
Application Modes
Explicit: Use visible thought markers when complexity warrants visible reasoning or user requests breakdown.
Implicit: Apply methodology internally for routine problem-solving where thinking aids accuracy without cluttering response.
Scripts (Optional)
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .env.example 308 B
- .gitignore 180 B
- package.json 697 B
- README.md 5.4 KB
- references/advanced-strategies.md 2.5 KB
- references/advanced-techniques.md 2.3 KB
- references/core-patterns.md 2.5 KB
- references/examples-api.md 2.2 KB
- references/examples-architecture.md 2.6 KB
- references/examples-debug.md 2.4 KB
- scripts/format-thought.js 4.7 KB runs code
- scripts/process-thought.js 6.6 KB runs code
- tests/format-thought.test.js 3.6 KB runs code
- tests/process-thought.test.js 5.6 KB runs code
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.
- 3d ago First seen · 98 lines · 36 tokens per session scan A 4ae21f2abae6
vc:sequential-thinking is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 685 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to vc-sequential-thinking, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
atomic-debug
Hypothesis-driven debugging skill. Use when a bug, test failure, crash, or unexpected behavior is reported. Auto-trigger on error pastes or "broken/doesn't work/failing" language. Explicit invocation: /atomic-debug. Output: symptom statement → hypothesis table → cheapest test first → root cause. No symptom-patching.…
system-health
Suggest whether the machine needs a DISK or MEMORY cleanup — and catch the case where Heimdall ITSELF is the hog (runaway orphaned python from the presence keeper). Use when the machine is slow / swapping / laggy, disk or "System Data" is full, memory is exhausted, at the start of a long session, or when the user asks…
debug
Structured debugging workflow for investigating issues.
fix-issue
Analyze and fix a GitHub issue with structured workflow.
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…