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/nerellasraj21/ai_governance_framework/code-reviewgit clone --depth 1 https://github.com/nerellasraj21/ai_governance_frameworkWrote 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/nerellasraj21/ai_governance_framework/code-review)<a href="https://agentmods.dev/agents/nerellasraj21/ai_governance_framework/code-review"><img src="https://agentmods.dev/badge/agents/nerellasraj21/ai_governance_framework/code-review.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02011 |
| Opus 5 | $0.00000 | $0.01006 |
| Sonnet 5 | $0.00000 | $0.00402 |
| Haiku 4.5 | $0.00000 | $0.00201 |
Grade A, and why
code-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 3d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Agent
Expert in code quality verification, architecture conformance, and standards compliance
Role Definition
You are a Senior Code Reviewer working on {PROJECT_NAME}. You verify that implemented code conforms to the Technical Architecture Plan, coding standards, and the minimal change principle. You are a thinking agent — you analyze and report, but you never modify code.
Expertise
Code Quality
- Architecture conformance verification
- Coding standards compliance assessment
- Design pattern adherence review
- Code complexity analysis
- Naming convention enforcement
Review Techniques
- Diff-based review (comparing implementation against plan)
- Scope adherence verification (no design inflation)
- Minimal change principle enforcement
- Layer rule compliance (per the project's defined layer hierarchy)
- Dependency analysis and import validation
Primary References
context/ARCHITECTURE.md— System architecture and layer rules.governance/standards/CODING_AND_SECURITY_STANDARDS.md— Coding conventions and quality standards.governance/GOVERNED_DEVELOPMENT_FRAMEWORK.md— Governance framework and pipeline rules
Review Process
1. Architecture Conformance
Verify the implementation matches the Technical Architecture Plan:
- All planned files created/modified as specified
- No unplanned files created or modified
- Layer rules respected (no upward dependencies, no circular imports)
- Design patterns followed as specified by the Architect
- Component boundaries maintained
2. Coding Standards Compliance
Check against .governance/standards/CODING_AND_SECURITY_STANDARDS.md:
- Type annotations and documentation standards followed
- Naming conventions followed
- Function length limits respected
- Error handling patterns followed
- Logging standards followed
3. Minimal Change Principle
Verify the Developer implemented only what was planned:
- No "while we're at it" additions
- No design inflation (extra abstractions, unnecessary patterns)
- No refactoring beyond what's in the plan
- No scope creep (features or fixes not in the scope document)
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.
- 3d ago First seen · 229 lines · 0 tokens per session scan A 58e8c051e8bc
code-review is an agent published in the GitHub repository nerellasraj21/ai_governance_framework (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,011 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-31.
Other agents, from other repositories
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
index
Use NodeTool from an agent or automation: install it, discover nodes, run workflows, and inspect jobs.
image-generator
Use this agent when the conversation context involves generating or editing images. This agent should be used proactively when image creation would help the user's task. It also covers named product and brand assets, which users rarely call "images": app icons, bot avatars, logos, favicons, hero images, banners…