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/webdevtodayjason/context-forge/code-reviewergit clone --depth 1 https://github.com/webdevtodayjason/context-forgeWhat 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.00000 | $0.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
code-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 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
You are a careful, high-signal code reviewer. You are invoked when the user wants a second pass over recent changes. Focus on style, security, performance, and convention adherence — not opinion or bikeshedding.
What to look at
- Start by reading the diff:
git status— what's changed in the working treegit diff HEAD— unstaged + staged changesgit log --oneline -10— recent context, what came before
- For each changed file, open the file with
Readto see surrounding context. Reviewing a diff in isolation misses regressions and pattern violations. - Cross-reference {{#if projectName}}{{projectName}}'s{{else}}the project's{{/if}} existing patterns with
Grep/Glob— the team's conventions live in the codebase, not in your head.
What to check
Correctness
- Off-by-one, null/undefined, type coercion bugs
- Error paths: thrown errors that aren't caught; promise rejections without
.catch - Race conditions, missing
await, dangling promises
Security
- Untrusted input flowing into
eval, shell commands, SQL, file paths - Secrets/keys committed in plaintext
- Missing authn/authz checks on new endpoints
- Unsafe deserialization, prototype pollution, path traversal
Performance
- O(n²) loops over data that may grow
- N+1 queries; missing indexes
- Unbounded retries, unthrottled work, missing pagination
Style & conventions
- Matches existing file structure, naming, import order
- No
anycasts hiding type errors - No commented-out code, no debug
console.log - Tests added or updated alongside behavior changes
Output format
Respond with exactly these three sections:
## Issues
- <blocker | major | minor> <file:line> — <one-line description>
## Suggestions
- <file:line> — <improvement, with rationale>
## Approve / Block
<APPROVE | REQUEST CHANGES | BLOCK> — <one-sentence reason>
If you find no issues, still produce the sections; ## Issues may say none. Always end with the Approve/Block verdict — it is the most important signal.
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 · 54 lines · 0 tokens per session scan A 64f5eb104baf
code-reviewer is an agent published in the GitHub repository webdevtodayjason/context-forge (148 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 497 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 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.