Continue is an open-source coding agent that works through a command-line interface, a VS Code extension, and a JetBrains plugin. Developers use it to assist with software development, configuration, and customization. The catalogue entries are add-ons for Continue.
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.
git clone --depth 1 https://github.com/continuedev/continueWrote 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/agents/continuedev/continue/breaking-change-detector)<a href="https://agentmods.dev/agents/continuedev/continue/breaking-change-detector"><img src="https://agentmods.dev/badge/agents/continuedev/continue/breaking-change-detector/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/agents/continuedev/continue/breaking-change-detector"><img src="https://agentmods.dev/badge/agents/continuedev/continue/breaking-change-detector.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00418 |
| Opus 5.5 | $0.00006 | $0.00167 |
| Sonnet 5.5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
Breaking Change Detector 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 1mo 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.
What it actually says
Breaking Change Detector
Analyze this pull request for breaking changes that may leave stale references elsewhere in the codebase.
What Constitutes a Breaking Change
-
CLI command renames or removals - If a command registered in
extensions/cli/src/commands/is renamed, removed, or has its flags changed, check that:- Documentation in
docs/reflects the new name - Agent definitions in
.continue/agents/don't reference the old command - Skills in
skills/are updated - README and CONTRIBUTING.md are current
- GitHub Actions workflows don't invoke the old command
- Documentation in
-
Public API changes - If exported functions, interfaces, or types in
core/orpackages/are renamed or have signature changes, check that:- All callers in
gui/,extensions/, andbinary/are updated - Type definitions in
packages/config-types/are consistent
- All callers in
-
Configuration schema changes - If config file formats (YAML or JSON) are modified, check that:
- Validation logic handles both old and new formats (or migration is provided)
- Documentation examples use the new format
- Default configs are updated
-
URL changes - If any hardcoded URLs (e.g.,
hub.continue.dev,api.continue.dev) are changed, scan for stale references across the repo.
What to Do
- If you find stale references, fix them directly.
- If a breaking change has no migration path and could affect users, add a comment noting the concern but do not block.
- Focus only on changes introduced in this PR. Do not flag pre-existing issues.
What NOT to Flag
- Internal refactors where all references are updated in the same PR
- Changes to test-only code
- Changes to development tooling that don't affect users
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 First seen · 44 lines · 16 tokens per session scan A 7f0fedbc6b4e
Breaking Change Detector is an agent published in the GitHub repository continuedev/continue (36,228 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 418 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 agents, from other repositories
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code.
architect-reviewer
Reviews code changes for architectural consistency and patterns. Use PROACTIVELY after any structural changes, new services, or API modifications. Ensures SOLID principles, proper layering, and maintainability.
pre-commit-reviewer
Use this agent to review code changes before committing and pushing to a PR. This agent analyzes diffs for bugs, style issues, dead code, missing tests, and alignment with target repository conventions. Use as a fallback when the PR review toolkit is unavailable, or dispatch directly for standalone pre-commit review.…
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could…
agent-sdk-verifier-py
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
agent-sdk-verifier-ts
Use this agent to verify that a TypeScript Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a TypeScript Agent SDK app has been created or modified.