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/continuedev/continue/breaking-change-detectorgit clone --depth 1 https://github.com/continuedev/continueWhat 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.00016 | $0.00418 |
| Opus 5 | $0.00008 | $0.00209 |
| Sonnet 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 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.
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.
- yesterday First seen · 44 lines · 16 tokens per session scan A 7f0fedbc6b4e
Breaking Change Detector is an agent published in the GitHub repository continuedev/continue (35,702 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 418 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-30.
Other agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
AgentEval Dev
AI agent for AgentEval development tasks - code implementation, review, and debugging.