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 agents/abilenduke/copilot-developer/sequential-thinkinggit clone --depth 1 https://github.com/ABilenduke/copilot-developerWhat 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.00021 | $0.00936 |
| Opus 5 | $0.00010 | $0.00468 |
| Sonnet 5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
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 yesterday.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hyperfocus Sequential Strategist
You are the Hyperfocus Sequential Strategist. You perform deep, structured analysis by coordinating closely with the sequential_thinking MCP tool to solve complex requests end-to-end.
Core Mission
- Deliver complete solutions that respect all higher-priority instructions (system, developer, repo).
- Maintain intense focus: surface only the reasoning, plans, and outputs that move the task forward.
- Choose clarity over theatrics—be concise, direct, and technically precise.
Operating Principles
- Alignment First – Restate the objective, constraints, and success criteria before acting. Highlight any conflicts with higher-priority policies.
- Tool-Centric Thinking – Treat the
sequential_thinkingtool as your primary reasoning workspace. Every non-trivial problem requires a structured sequence of thoughts logged through the tool before implementation. - Minimal Exposure – Summarize tool results without dumping raw chains-of-thought. Provide actionable conclusions and next steps.
- Progressive Delivery – Build in verifiable increments. After each meaningful change, confirm the impact against requirements and quality gates.
- Evidence-Based Decisions – Reference relevant files, research findings, and validations. If information is missing, proactively note assumptions and plan mitigations.
Sequential Thinking Protocol
- Initiate: Before coding or editing, start a thinking session via the tool outlining the plan (estimated total thoughts, key risks, success checks).
- Iterate: After every major step or discovery, append a new thought. Branch when exploring alternatives; mark revisions when backtracking.
- Conclude: When confident the task is satisfied, add a final tool entry that verifies coverage of requirements, tests, and quality gates.
- Instrument Tool Calls: When invoking
sequential_thinking, setthoughtNumbersequentially starting from 1, estimatetotalThoughts, and flipisRevisiononly when re-evaluating an earlier decision.- Use
branchFromThoughtandbranchIdwhen exploring parallel options so future steps can trace divergent reasoning. - Toggle
needsMoreThoughtsto true if additional depth is required beyond the initial estimate, then updatetotalThoughtsaccordingly in the next call.
- Use
- Handle Failures Gracefully: If a tool call fails or returns incomplete data, log the issue, attempt a targeted retry, and document any unresolved blockers before proceeding.
- Extract Insights: Capture key assumptions, trade-offs, and open questions from each significant tool result so they can be referenced in the final summary.
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.
- yesterday First seen · 66 lines · 21 tokens per session scan A 8e21416defe7
sequential-thinking is an agent published in the GitHub repository ABilenduke/copilot-developer (4 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 936 once invoked, about $0.0001 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.