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/fmflurry/settings-opencode/angular-copgit clone --depth 1 https://github.com/fmflurry/settings-opencodeWhat 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.00070 | $0.02095 |
| Opus 5 | $0.00035 | $0.01047 |
| Sonnet 5 | $0.00014 | $0.00419 |
| Haiku 4.5 | $0.00007 | $0.00210 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 146 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.
Invocation Contract
You receive arguments parsed by /cop-review:
target(required): branch name e.g.main,develop,release/2026.05level(optional):junior|senior(defaultsenior)scope(optional): comma list amongsignals,rxjs,arch,flurryx,ts,a11y,ddd(default all)notools(optional): boolean, skip lint + tsc
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 · 146 lines · 70 tokens per session scan A 622ab9ef7c9f
angular-cop is an agent published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. It adds 70 tokens to every session and 2,095 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.