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/fmflurry/settings-opencodeWrote 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/commands/fmflurry/settings-opencode/cop-review)<a href="https://agentmods.dev/commands/fmflurry/settings-opencode/cop-review"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/cop-review/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/commands/fmflurry/settings-opencode/cop-review"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/cop-review.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.00000 | $0.01185 |
| Opus 5.5 | $0.00000 | $0.00474 |
| Sonnet 5.5 | $0.00000 | $0.00237 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
cop-review 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cop-review — Pre-Merge Review
Review the current branch against a target branch before merging. Stack-aware: code-reviewer loads the matching cop skill based on the detected project type. Loads AGENTS.md from cwd. Runs tooling checks. Emits tiered report.
Usage
/cop-review <target-branch> [--level=junior|senior] [--scope=...] [--no-tools]
Arguments
<target-branch>(required) — the branch the PR will merge into (e.g.main,develop,release/2026.05).--level=junior— verbose teaching mode with rationale + doc links for every finding.--level=senior(default) — terse one-liners.--scope=...— limit to a subset of checklists. Comma list. Defaults to all; on .NET,dddis auto-enabled when the diff touches domain files.--no-tools— skip tooling checks and produce static review only (faster).
Stack detection & skill loading
Before loading a skill, detect the project stack by checking these signals in cwd (search recursively):
| Signal | Stack | Skill to load | Tooling |
|---|---|---|---|
angular.json present |
Angular + TypeScript | angular-cop |
npx tsc --noEmit + npm run lint |
*.csproj / *.sln / *.slnx / global.json present |
.NET | dotnet-cop |
dotnet build --nologo -clp:ErrorsOnly + dotnet format --verify-no-changes |
If BOTH are present (rare monorepo), check which language the diff files are in (.ts/.html → angular-cop; .cs/.csproj → dotnet-cop). If still ambiguous, default to angular-cop and note the ambiguity in the report header.
code-reviewer executes this command directly and loads the applicable skill(s) itself. Never route through the angular-cop/dotnet-cop agents or conductor.
Domain-diff default scope (.NET)
When the .NET diff touches domain files — paths under **/*.Domain/**, **/Domain/**, or **/Core/** — add ddd to the effective scope automatically, without waiting for an explicit --scope=ddd. The dotnet-cop skill then loads dotnet-ddd (review-checklist.md) for domain-layer findings. --scope=ddd still forces DDD checks when no domain file is detected.
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 · +42 lines ebd8f815f95c
- 1mo ago First seen · 45 lines · 0 tokens per session scan A 0dc469fe47c3
cop-review is a command published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,185 tokens. 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 commands, from other repositories
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-tag
Create and push a version tag after a release PR has been merged.
factory
Linha de montagem multi-agente (Software Factory) — spec-writer → builder em worktree isolado → 4 revisores paralelos (Security, Code, UI, UX) → approver com gate de risco e dashboard visual.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.