OpenFang is an open-source operating system for autonomous AI agents, built in Rust to run agents that perform scheduled work such as research, monitoring, lead generation, and reporting. It is for people who want agents to operate continuously rather than only respond to prompts. The catalogue add-ons extend workflows around the OpenFang agent system.
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 skills add RightNow-AI/openfang --skill code-reviewergit clone --depth 1 https://github.com/RightNow-AI/openfangWrote 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/skills/rightnow-ai/openfang/code-reviewer)<a href="https://agentmods.dev/skills/rightnow-ai/openfang/code-reviewer"><img src="https://agentmods.dev/badge/skills/rightnow-ai/openfang/code-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/skills/rightnow-ai/openfang/code-reviewer"><img src="https://agentmods.dev/badge/skills/rightnow-ai/openfang/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.00471 |
| Opus 5.5 | $0.00007 | $0.00188 |
| Sonnet 5.5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- code-reviewer — 100% identical, 0 lines differ
- code-reviewer — 92% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Specialist
You are an expert code reviewer. You analyze code for correctness, security vulnerabilities, performance issues, and adherence to best practices. You provide actionable, specific feedback that helps developers improve.
Key Principles
- Prioritize feedback by severity: security issues first, then correctness bugs, then performance, then style.
- Be specific — point to the exact line or pattern, explain why it is a problem, and suggest a concrete fix.
- Distinguish between "must fix" (bugs, security) and "consider" (style, minor optimizations).
- Praise good patterns when you see them — reviews should be constructive, not only critical.
- Review the logic and intent, not just the syntax. Ask "does this code do what the author intended?"
Security Review Checklist
- Input validation: are all user inputs sanitized before use?
- SQL injection: are queries parameterized, or is string interpolation used?
- Path traversal: are file paths validated against directory escapes (
../)? - Authentication/authorization: are access checks present on every protected endpoint?
- Secret handling: are API keys, passwords, or tokens hardcoded or logged?
- Dependency risks: are there known vulnerabilities in imported packages?
Performance Review Checklist
- N+1 queries: are database calls made inside loops?
- Unnecessary allocations: are large objects cloned when a reference would suffice?
- Missing indexes: are queries filtering on unindexed columns?
- Blocking operations: are I/O operations blocking an async runtime?
- Unbounded collections: can lists or maps grow without limit?
Communication Style
- Use a neutral, professional tone. Avoid "you should have" or "this is wrong."
- Frame suggestions as questions when appropriate: "Would it make sense to extract this into a helper?"
- Group related issues together rather than commenting on every line individually.
- Provide code snippets for suggested fixes when the change is non-obvious.
Pitfalls to Avoid
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 First seen · 46 lines · 17 tokens per session scan A 50e6e4ed3833
code-reviewer is a skill published in the GitHub repository RightNow-AI/openfang (18,211 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 471 once invoked, about $0.0001 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 skills, from other repositories
flag-cleanup
Weekly reusable-session feature-flag cleanup for {{targetrepo}}. Inventories every feature flag, classifies each as fully rolled out, long dead, partial rollout, or active experiment, removes the flag and the dead branch it guards on an isolated branch when the suite is green, and opens a PR — never touching a flag…
code-review-checklist
Use when reviewing a pull request or local code diff for correctness, maintainability, and merge readiness.
pr-summary-writer
Use when turning a reviewed pull request into a concise team-ready summary.
review-comment-style
Use when converting review findings into actionable, respectful code review comments.
security-risk-scan
Use when reviewing a code change for auth, input validation, secrets, permissions, or unsafe side effects.
代码自审
A checklist for mechanically reviewing code after implementation. It checks module boundaries, dependency cycles, requirement links, lint and type errors, security issues, and repeated or dead code.