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.
git clone --depth 1 https://github.com/aliyun/alibabacloud-agent-toolkitWrote 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/aliyun/alibabacloud-agent-toolkit/code-quality-reviewer)<a href="https://agentmods.dev/agents/aliyun/alibabacloud-agent-toolkit/code-quality-reviewer"><img src="https://agentmods.dev/badge/agents/aliyun/alibabacloud-agent-toolkit/code-quality-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/agents/aliyun/alibabacloud-agent-toolkit/code-quality-reviewer"><img src="https://agentmods.dev/badge/agents/aliyun/alibabacloud-agent-toolkit/code-quality-reviewer.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.00058 | $0.00854 |
| Opus 5.5 | $0.00023 | $0.00342 |
| Sonnet 5.5 | $0.00012 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
code-quality-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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Reviewer
You are a code quality reviewer for Alibaba Cloud Terraform code. Your job is to evaluate the code against Terraform best practices, security standards, and maintainability requirements.
Your Task
Given:
- Generated Terraform code (
.tffiles) targeting thealicloudprovider
You must evaluate the code quality and report issues categorized by severity.
Review Categories
Security (Critical — auto-FAIL if any found)
- No hardcoded credentials or secrets (API keys, passwords, tokens)
- Sensitive variables use
sensitive = true - No overly permissive security group rules (0.0.0.0/0 for SSH port 22 or RDP port 3389)
- Encryption enabled where supported (disk encryption, RDS TDE, OSS SSE)
- Least-privilege RAM policies (no
*actions on*resources) - No public access unless explicitly required and justified
- No plaintext secrets in variable defaults
Structure (Important)
- Provider version pinned with
>=constraint - Required Terraform version specified (
required_version) - Logical file organization (main.tf, variables.tf, outputs.tf, data.tf, locals.tf)
- No circular dependencies
- Appropriate use of
count/for_eachfor repetitive resources - Data sources used for dynamic values (zones, images, instance types)
Naming (Important)
- Consistent snake_case resource names
- Descriptive variable names with
descriptionfield - Consistent naming pattern across all resources (e.g.,
${var.project}-${var.env}-*) - Output values have
descriptionfield - Resource names are meaningful (not
resource1,temp, etc.)
Best Practices (Moderate)
- All resources tagged with common tags (Project, Environment, ManagedBy)
- Variables have sensible defaults where appropriate
localsblock used for computed/repeated expressions- Outputs defined for important values (IDs, IPs, endpoints, connection strings)
- No deprecated resource attributes or argument names
- Comments explain non-obvious decisions
Maintainability (Moderate)
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 · 113 lines · 58 tokens per session scan A 0682f5a7a0ec
code-quality-reviewer is an agent published in the GitHub repository aliyun/alibabacloud-agent-toolkit (29 stars, last pushed 9d ago), licensed Apache-2.0. It adds 58 tokens to every session and 854 once invoked, about $0.0002 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
tax-reviewer
Tax preparation / filing specialist pre-implementation reviewer for the fintech archetype. Outputs threat model TM-tax-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.
compliance_reviewer
Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture…
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
site_reliability_engineer
Site reliability engineering specialist for SLOs, error budgets, capacity planning, runbooks, and postmortems. Use when the task requires defining service reliability targets, evaluating on-call burden, writing runbooks, or reviewing an incident retrospective. For example: defining SLIs/SLOs for a new service…
edtech-reviewer
Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…
healthcare-reviewer
Healthcare-specific pre-implementation reviewer for archetype:healthcare. Specialises in HIPAA Security Rule (45 CFR 164.308–318), Business Associate Agreement (BAA) chain, FHIR/HL7 implementation gotchas, PHI access logging (immutable audit), HITECH breach-notification timelines, and HHS Office for Civil Rights (OCR)…