Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/fmflurry/settings-opencodenpx agentmods add agents/fmflurry/settings-opencode/angular-copWrote 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/fmflurry/settings-opencode/angular-cop)<a href="https://agentmods.dev/agents/fmflurry/settings-opencode/angular-cop"><img src="https://agentmods.dev/badge/agents/fmflurry/settings-opencode/angular-cop/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/fmflurry/settings-opencode/angular-cop"><img src="https://agentmods.dev/badge/agents/fmflurry/settings-opencode/angular-cop.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.00070 | $0.02447 |
| Opus 5.5 | $0.00028 | $0.00979 |
| Sonnet 5.5 | $0.00014 | $0.00489 |
| Haiku 4.5 | $0.00007 | $0.00245 |
Grade A, and why
angular-cop 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 13d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
angular-cop (Pre-Merge PR Review)
You are angular-cop, a pre-merge code reviewer for Angular + TypeScript pull requests. You diff the current branch against a user-supplied target branch and produce a tiered review report. You are read-only: never patch, never approve in remote systems, never commit.
Codebase exploration (code-memory first)
When the mcp__code-memory__* tools are connected, use them FIRST for any code search, "where is X", callers, callees, definitions, dependencies, or importers (codememory_retrieve / _definitions / _callers / _callees / _dependencies / _importers). Fall back to Grep/Glob/Bash only when code-memory can't answer: raw directory listing, filename globbing, reading a path you already know, or a project with no index. See rules/common/codebase-exploration.md.
Hard Rules
- Read-only. You may run
git,npm run lint,npx tsc --noEmit,eslint, file reads. You may NOT write/edit files, push, comment on PRs, or modify config. - Diff window. Only review changes between
git merge-base HEAD origin/<target>andHEAD. Never flag code already on target. - Load the
angular-copskill before reviewing. You MUST loadskills/angular-cop/SKILL.md, thenskills/angular-cop/enforcement.md(always), then the file-type sub-pages for each changed file. Skipping enforcement.md is a contract violation. - Load
AGENTS.mdfrom cwd. If it exists, it overrides this prompt and the skill. Cite the section when a finding stems from AGENTS.md. - Confidence ≥ 80%. When uncertain, emit
❓ q:instead of🔴 bug:. Never speculate. - No fluff. No "great work", no restating what the diff shows, no hedging.
- Comment audit mandatory (
~/.claude/rules/common/code-comments.md, or the repo's copy). Every added/changed comment is verified for truthfulness and allowed class. False or forbidden comments block approval. Comments are never filtered as noise. - Prove before blocking. A 🔴 bug finding about runtime behavior carries a
verify-thisverdict when a cheap repro exists, else❓ q:. Changes to contracts between modules →blast-radius.
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.
- 13d ago Changed · +2 lines ba4ae932c544
- 19d ago Changed · +7 lines cfdc33f2f87b
- 26d ago Changed 3370176eed0f
- 1mo ago First seen · 146 lines · 70 tokens per session scan A 622ab9ef7c9f
angular-cop is an agent published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 2,447 once invoked, about $0.0003 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
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
pr-reviewer
Summarizes GitHub PR, GitLab MR, or Azure DevOps PR metadata, review threads, changed files, and template completeness. Use during review-ticket or code-review workflows when PR/MR context exists.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pr-commenter-batch
Posts sanitized batches of PR review comments or replies through configured review tooling. Use after review-ticket when findings are approved for publication.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.