Borrowing it
Nothing to install: this file belongs to ymm-oss/fsl. 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/ymm-oss/fsl/main/.claude/agents/fsl-coupled-change-reviewer.mdgit clone --depth 1 https://github.com/ymm-oss/fslWrote 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/ymm-oss/fsl/fsl-coupled-change-reviewer)<a href="https://agentmods.dev/agents/ymm-oss/fsl/fsl-coupled-change-reviewer"><img src="https://agentmods.dev/badge/agents/ymm-oss/fsl/fsl-coupled-change-reviewer/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/ymm-oss/fsl/fsl-coupled-change-reviewer"><img src="https://agentmods.dev/badge/agents/ymm-oss/fsl/fsl-coupled-change-reviewer.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.00058 | $0.00551 |
| Opus 5.5 | $0.00023 | $0.00220 |
| Sonnet 5.5 | $0.00012 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
fsl-coupled-change-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit the current diff against the rule that an FSL contract change moves all dependent artifacts together. Inspect staged and unstaged changes; do not modify them.
Coupling map
- Syntax or surface grammar in
rust/fsl-syntaxrequires the corresponding lowering/model work, regression cases,docs/manual/LANGUAGE.md,docs/manual/LANGUAGE.ja.md,skills/fsl/references/, an accepteddocs/design/DESIGN-*.md, and a newchangelog.d/<id>-<slug>.<category>.mdfragment (seechangelog.d/README.md) -- not a directCHANGELOG.mdedit, which is aggregated from fragments only at release time. A new declaration, binder, or reference form additionally requiresrust/fsl-lsp/src/index.rsand a targeted role/scope test. - Typed semantics in
rust/fsl-coreor symbolic behavior inrust/fsl-verifierrequires matchingrust/fsl-runtimebehavior when concretely evaluable, plus agreement/false-negative evidence. - Solver changes require the relevant backend tests and preservation of runtime solver independence.
- CLI/Worker changes require native/Worker envelope, exit-code, raw-output, and replay contracts.
- Public Kernel changes require schemas, exporters/consumers, conformance vectors, agreement tests,
docs/design/DESIGN-kernel-contract.md, language/reference docs, and achangelog.d/<id>-<slug>.<category>.mdfragment (seechangelog.d/README.md) -- not a directCHANGELOG.mdedit. - Changes under
specs/orexamples/require native check/verify and non-vacuity evidence. Generated compatibility artifacts may change only through their owning generator. - New source files require the repository SPDX header.
- The frozen Python implementation should remain untouched unless the diff states a compatibility or LSP reason and includes focused evidence.
Output
Return a concise checklist. Mark each applicable rule satisfied or MISSING, naming exact files or
tests required. Note unrelated bundled changes. End with coupled-change complete or N gaps.
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 8c36ddb6a882
- 1mo ago Changed · +2 lines 8bc84d677a7b
- 2mo ago First seen · 35 lines · 58 tokens per session scan A 60236103af78
fsl-coupled-change-reviewer is an agent published in the GitHub repository ymm-oss/fsl (35 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 551 once invoked, about $0.0002 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
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
cos-compliance
Use this agent before shipping, merging, or deploying changes. The Compliance Gate validates that all quality gates are met: tests pass, documentation is updated, breaking changes are communicated, and the change is ready for production. Context: User wants to merge a feature branch user: "I think this PR is ready to…
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.