Test Guard
amElnagdy/guard-skills
Reviews newly written or edited tests against nine rules that cut test bloat, such as mock-heavy checks and near-duplicate cases, before they are committed.
TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring.
Install Moai Foundation Quality
$ npx skills add modu-ai/moai-adk --skill moai-foundation-quality -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install modu-ai/moai-adk moai-foundation-quality --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/moai-foundation-quality .claude/skills/moai-foundation-quality && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "moai-foundation-quality" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-foundation-quality into .claude/skills/moai-foundation-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-foundation-quality", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-foundation-qualityType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add modu-ai/moai-adk --skill moai-foundation-quality -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install modu-ai/moai-adk moai-foundation-quality --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/moai-foundation-quality .agents/skills/moai-foundation-quality && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "moai-foundation-quality" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-foundation-quality into .agents/skills/moai-foundation-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-foundation-quality", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add modu-ai/moai-adk --skill moai-foundation-quality -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install modu-ai/moai-adk moai-foundation-quality --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/moai-foundation-quality .cursor/skills/moai-foundation-quality && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "moai-foundation-quality" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-foundation-quality into .cursor/skills/moai-foundation-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-foundation-quality", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/modu-ai/moai-adk.git --path .claude/skills/moai-foundation-quality--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add modu-ai/moai-adk --skill moai-foundation-quality -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install modu-ai/moai-adk moai-foundation-quality --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/moai-foundation-quality .gemini/skills/moai-foundation-quality && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "moai-foundation-quality" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-foundation-quality into .gemini/skills/moai-foundation-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-foundation-quality", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install modu-ai/moai-adk moai-foundation-qualityInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add modu-ai/moai-adk --skill moai-foundation-quality -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/moai-foundation-quality .github/skills/moai-foundation-quality && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "moai-foundation-quality" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-foundation-quality into .github/skills/moai-foundation-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-foundation-quality", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add modu-ai/moai-adk --skill moai-foundation-quality -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install modu-ai/moai-adk moai-foundation-quality --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modu-ai/moai-adk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/moai-foundation-quality .opencode/skills/moai-foundation-quality && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "moai-foundation-quality" agent skill from https://github.com/modu-ai/moai-adk/tree/main/.claude/skills/moai-foundation-quality into .opencode/skills/moai-foundation-quality/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "moai-foundation-quality", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
moai-foundation-quality- GitHub stars
- 1.2k
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,260 words
- Files
- 7 (incl. references)
- Skills in repo
- 48
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring.
- Quality gate checks
- SKILL.md covers Quick Reference, The MoAI Quality Model, TRUST 5 Principles and Quality Gates and the 3-Level…, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Coverage targets
What it does
Moai Foundation Quality is an agent skill from modu-ai/moai-adk. TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring. Use for code review, quality gate checks, coverage targets, or TRUST 5 compliance.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `modules/best-practices.md`, `modules/integration-patterns.md` and `modules/proactive-analysis.md`). Compatibility notes: Designed for Claude Code
It sits in Testing & QA, covering Quality gates. The repository describes itself as: Agentic development harness for Claude Code — SPEC-driven plan/run/sync, TRUST 5 quality gates, model+effort routing, and Claude×GLM multi-LLM cost control. Single Go binary, 16… The licence is Apache-2.0.
When your agent uses it
- Quality gate checks
- Coverage targets
- TRUST 5 compliance
Example prompts
- “/moai-foundation-quality”
Requirements
- Python 3
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Grep, Glob
What it can do on your machine
Read from SKILL.md and the folder at commit 2aab5f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlob
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Moai Foundation Quality loads about 2.9k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 1,260 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from modu-ai/moai-adk at commit 2aab5f7, republished under its Apache-2.0 licence (© modu-ai). 1,260 words, ~2,887 tokens.
Download SKILL.mdSave it as
.claude/skills/moai-foundation-quality/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- moai-foundation-quality
- description
- TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring. Use for code review, quality gate checks, coverage targets, or TRUST 5 compliance.
- allowed-tools
- Read, Grep, Glob
- compatibility
- Designed for Claude Code
- when_to_use
- Use for code-quality guidance: TRUST 5 principles (Tested, Readable, Unified, Secured, Trackable), the 3-level harness (minimal/standard/ thorough), /moai…
- license
- Apache-2.0
- user-invocable
- false
- metadata.version
- 3.0.0
- metadata.category
- foundation
- metadata.status
- active
- metadata.updated
- 2026-07-10
- metadata.modularized
- true
- metadata.tags
- foundation, quality, testing, validation, trust-5, best-practices, code-review
- metadata.aliases
- moai-foundation-quality
TRUST 5 Quality Principles and Enforcement
This skill provides background knowledge on MoAI's quality model: the five
TRUST 5 principles, how agents enforce them, the 3-level harness, and the
language-aware toolchains that /moai gate runs. MoAI does NOT ship a
quality-validation library — quality is enforced through agents
(manager-develop, sync-auditor), slash commands (/moai gate,
/moai review), and the harness (minimal/standard/thorough).
Quick Reference
TRUST 5 Principles (Tested, Readable, Unified, Secured, Trackable) are quality dimensions, not code objects. Every code change is evaluated against all five.
Quality Mechanisms (the real enforcement layer):
/moai gate— runs lint + format + type-check + test in parallel as a pre-commit quality gate (<30s). Auto-detects the project language and runs the appropriate toolchain.manager-develop(run-phase) — implements viacycle_type∈ {tdd, ddd, autofix}; the chosen cycle shapes how tests and behavior are produced.sync-auditor— independent skeptical quality assessment with 4-dimension scoring (Functionality, Security, Craft, Consistency), scored as the harmonic mean of dimensions, not the average.- 3-level harness — minimal (fast validation), standard (default checks), thorough (full sync-auditor + TRUST 5). Auto-determined by the Complexity Estimator based on SPEC scope.
- LSP quality gates — phase-specific thresholds (run: zero errors/type-errors/ lint-errors; sync: zero errors, max 10 warnings, clean LSP).
The MoAI Quality Model
MoAI does not provide a Python SDK or any library for quality validation. Quality is enforced through the workflow, the agents, and the gate commands. This skill documents how those pieces fit together so a Claude invocation can reason about quality correctly.
How TRUST 5 is enforced per phase
| Phase | Quality check | Owner |
|---|---|---|
| plan | Capture LSP baseline; identify quality risks in the plan | manager-spec |
| run | Zero errors/type-errors/lint-errors; tests pass; coverage met | manager-develop (cycle_type shapes the approach) |
| sync | Lint clean (≤10 warnings); docs updated; TRUST 5 re-affirmed | manager-docs, then sync-auditor scores |
| audit | Independent 4-dimension scoring (Functionality/Security/Craft/Consistency) | sync-auditor |
cycle_type and quality (manager-develop)
The run-phase cycle_type selects how quality is built in:
- tdd — Test-Driven Development (RED-GREEN-REFACTOR). Behavior is specified by a failing test first, then implemented. Best for new features.
- ddd — Domain-Driven refactoring (ANALYZE-PRESERVE-IMPROVE). Behavior-preserving transformation of existing code. Best for refactoring and debt reduction.
- autofix — diagnostic-driven fixing (LSP / lint / type errors). Best for
/moai fixand regression recovery.
See Skill("moai-workflow-tdd"), Skill("moai-workflow-ddd"), and Skill("moai-workflow-loop") for the per-cycle mechanics.
TRUST 5 Principles
TRUST 5 is a mnemonic for five quality dimensions. Treat each as a question to ask of any change, not a score to compute.
- T — Tested: Does the change have tests? Are they green? Is coverage at or above the project threshold (85%+ by default)? For existing untested code, are characterization tests capturing current behavior?
- R — Readable: Is naming clear? Are comments in English (or the configured code-comments language)? Could a new contributor follow the logic without a walkthrough?
- U — Unified: Does the change match the file's existing conventions (naming, error handling, imports)? Is it formatted with the project's formatter? Consistency within a file beats personal preference.
- S — Secured: Are all external inputs validated? Does it follow OWASP guidance for web security? Are credentials kept out of version control (environment variables instead)? See moai-ref-owasp-checklist.
- T — Trackable: Does the commit follow Conventional Commits? Does it reference the SPEC / issue it implements? Can the change be traced back to a requirement?
For the per-principle assessment checklist and the "not applicable" guard, see TRUST 5 Principles.
Quality Gates and the 3-Level Harness
The harness level controls how deep quality validation goes. It is auto-determined by the Complexity Estimator based on SPEC scope.
| Level | What runs | When |
|---|---|---|
| minimal | Fast validation only (lint + type + test) | Small SPECs, low risk |
| standard | Default checks (lint + type + test + format) | Most SPECs |
| thorough | Full sync-auditor + 4-dimension TRUST 5 scoring | Large SPECs, high risk |
/moai gate is the lightweight pre-commit entry point: it runs lint +
format + type-check + test in parallel and applies no fixes. It is the
fastest way to get a quality signal. For deeper review use /moai review.
Language-Aware Toolchains
The quality gate auto-detects the project language and runs the appropriate toolchain. Tools that are not installed are skipped gracefully; projects with no recognized language marker pass the gate silently. This skill is language-neutral — the 16 supported languages are treated equally.
| Language | Lint | Format | Test |
|---|---|---|---|
| Go | go vet → golangci-lint | gofmt | go test |
| Python | ruff | black | pytest |
| TypeScript / JavaScript | eslint | prettier | jest / mocha |
| Rust | cargo clippy | rustfmt | cargo test |
| Java / Kotlin | (per project linter) | (per project) | junit |
| Ruby | rubocop | rubocop | rspec |
| PHP | phpstan / phpcs | php-cs-fixer | pest / phpunit |
| ... | (16 languages supported; auto-detected) |
For the full toolchain mapping and how /moai gate detects the language,
see Language-Aware Toolchains.
Show full SKILL.md (528 more words)Show less
Module Reference
Each module is loaded on demand. Load the one relevant to the current task.
- TRUST 5 Principles — the five dimensions as assessment questions, per-principle checklists, and the "not applicable" guard.
- Proactive Analysis — how
/moai gate,/moai review, and/moai loopsurface quality issues proactively, and how to triage findings. - Best Practices — using WebSearch / WebFetch for up-to-date framework/library best practices, and validating against them.
- Integration Patterns — how quality fits into the SPEC workflow phases (plan/run/sync) and the harness levels.
Reference Files
- examples.md — worked TRUST 5 assessment examples and gate/review triage walkthroughs. Load when applying TRUST 5 to a concrete change.
- reference.md — the quality-mechanism reference: harness level detail, language toolchain table, agent roles, and the sync-auditor scoring model. Load when you need the authoritative mapping.
Works Well With
Agents (see .moai/config/sections/delegation.yaml for the 13-agent catalog):
manager-develop— run-phase implementation; owns the Tested and Unified principles through cycle_type.sync-auditor— independent 4-dimension quality scoring (Functionality / Security / Craft / Consistency).Explore(Anthropic built-in) — read-only codebase exploration before assessing quality.
Skills:
moai-foundation-core— TRUST 5 framework cross-reference and SPEC workflow foundations.moai-ref-testing-pyramid— test-pyramid strategy, coverage targets, and test patterns.moai-ref-owasp-checklist— OWASP Top 10 security checklist for the Secured principle.moai-workflow-tdd/moai-workflow-ddd/moai-workflow-loop— the cycle_type workflows that manager-develop uses.
Commands:
/moai gate— pre-commit quality gate (lint + format + type + test)./moai review— code review with security and MX-tag compliance./moai fix— auto-detect and fix LSP/lint/type errors./moai loop— iterative fix loop until resolved or max iterations.
<!-- moai:evolvable-start id="rationalizations" -->Common Rationalizations
| Rationalization | Reality |
|---|---|
| "The linter warnings are false positives" | False positives should be suppressed with inline comments. Ignoring them trains the team to ignore real issues. |
| "Security scanning can wait until before release" | Security vulnerabilities compound. Late discovery means expensive rework. Scan continuously. |
| "Coverage is high enough, the remaining 15% is edge cases" | Edge cases are where production bugs live. The uncovered code is the riskiest code. |
| "Code review is subjective, automation is sufficient" | Automation catches syntax and patterns. Reviews catch design flaws, naming confusion, and missing abstractions. |
| "TRUST 5 is too bureaucratic for a hotfix" | Hotfixes without quality gates introduce the next hotfix. TRUST 5 on a hotfix is the minimum, not the maximum. |
Chesterton's Fence: Before removing a quality check, understand why it was added. Removing a gate without understanding its history repeats the failure it was designed to prevent.
Shift Left: The earlier a defect is found, the cheaper it is to fix. Quality checks belong in the development loop, not at the end of it.
<!-- moai:evolvable-end --><!-- moai:evolvable-start id="red-flags" -->Red Flags
- Linter or type-checker warnings suppressed globally instead of per-line
- OWASP checklist not consulted when handling user input or authentication
- Coverage report not generated for a commit that adds new functionality
- TRUST 5 dimension skipped with "not applicable" without justification
- Quality report generated but no action taken on identified issues
<!-- moai:evolvable-end --><!-- moai:evolvable-start id="verification" -->Verification
- Linter runs clean or remaining warnings have inline suppression comments with reasons (show the command output)
- OWASP checklist reviewed for security-relevant changes (show checklist references)
- Coverage report generated and threshold met (show tool output)
- All five TRUST 5 dimensions assessed (show assessment for each)
- Quality findings triaged with a resolution plan for each
- No global rule disabling in linter configuration
<!-- moai:evolvable-end -->© modu-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (references) in .claude/skills/moai-foundation-quality of modu-ai/moai-adk.
- SKILL.md
- modules/best-practices.md
- modules/integration-patterns.md
- modules/proactive-analysis.md
- modules/trust5-validation.md
- references/examples.md
- references/reference.md
Open the folder on GitHubat commit 2aab5f7
Compare with similar skills
Moai Foundation Quality next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Moai Foundation Quality this skillmodu-ai/moai-adk | 1.2k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Test GuardamElnagdy/guard-skills | 1.3k | 2 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Triage Sonarqubenetdata/netdata | 81k | — | ~2.8k | Automated safety check: Notes | GPL-3.0 | |
| Sonarqube Analysishbmartin/graphviz2drawio | 275 | — | ~508 | Automated safety check: Notes | GPL-3.0 | |
| Code SolvingHoangTheQuyen/think-better | 122 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Trellis Finish WorkOrtonY/smart-resume | 122 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Triage Sonarqube
netdata/netdata
Inspect, review, or apply authorized triage decisions to SonarCloud issues and security hotspots; also review the Sonar helpers.
Sonarqube Analysis
hbmartin/graphviz2drawio
Inspect SonarQube Cloud/SonarCloud findings for this repository using local .env credentials.
Code Solving
HoangTheQuyen/think-better
Structured coding workflow for non-trivial code work: debug, build features, refactor, optimize, migrate and review code through 7 steps with evidence-based quality gates.
Trellis Finish Work
OrtonY/smart-resume
Wrap up the current session: verify quality gate passed, archive completed tasks, record session progress, push branch, and create PR.
lo2cin4bt Acceptance Review
lo2cin4/lo2cin4bt
Runs a pass, revise or block acceptance review on lo2cin4bt work, checking a deliverable against the request, repo contracts, tests, docs and the public GitHub boundary.
More from modu-ai/moai-adk
All 48 skills in this repoSVG Technical Infographic Author
modu-ai/moai-adk
Builds hand-editable SVG diagrams from computed layout coordinates, lints the source and renders a 2x PNG, with rules for when mermaid is the better choice.
MoAI Foundation Core
modu-ai/moai-adk
Reference for MoAI-ADK's core development principles: TRUST 5 quality gates, SPEC-first domain-driven workflow, agent delegation and token budgeting.
MoAI SPEC Workflow
modu-ai/moai-adk
Manages SPEC documents for MoAI-ADK development, with GEARS or EARS requirement notation, acceptance criteria and a link into the Plan-Run-Sync workflow.
MoAI TDD Workflow
modu-ai/moai-adk
Drives test-first development through the RED, GREEN, REFACTOR cycle, with a config switch that selects between TDD and a DDD workflow for existing code.
MoAI Worktree Management
modu-ai/moai-adk
Gives each SPEC its own Git worktree with a registry of active workspaces, base-branch sync and cleanup of merged ones, inside the MoAI-ADK workflow.
CI Watch and Auto-Fix Loop
modu-ai/moai-adk
Watches a pull request's CI checks after creation, separates required from auxiliary failures, applies limited safe fixes and escalates anything semantic to you.
Related
Categories
Questions about Moai Foundation Quality
What does Moai Foundation Quality do?
TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring. Moai Foundation Quality is an agent skill from modu-ai/moai-adk. TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring.
When should I use Moai Foundation Quality?
Moai Foundation Quality fits situations like: quality gate checks; coverage targets; TRUST 5 compliance.
How do I install Moai Foundation Quality in Claude Code?
Run `npx skills add modu-ai/moai-adk --skill moai-foundation-quality -a claude-code`. Or copy the skill folder (.claude/skills/moai-foundation-quality in modu-ai/moai-adk) into .claude/skills/moai-foundation-quality in your project. Claude Code loads it when a task matches its description.
How do I install Moai Foundation Quality in Codex?
Run `npx skills add modu-ai/moai-adk --skill moai-foundation-quality -a codex`. Or copy the skill folder (.claude/skills/moai-foundation-quality in modu-ai/moai-adk) into .agents/skills/moai-foundation-quality in your project. Codex loads it when a task matches its description.
Can I use Moai Foundation Quality in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add modu-ai/moai-adk --skill moai-foundation-quality -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/moai-foundation-quality, .gemini/skills/moai-foundation-quality, .github/skills/moai-foundation-quality and .opencode/skills/moai-foundation-quality in your project.
What does Moai Foundation Quality need to run?
SKILL.md names no scripts, command-line tools or credentials: Moai Foundation Quality is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Grep, Glob. Compatibility (from SKILL.md): Designed for Claude Code.
Does Moai Foundation Quality access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Moai Foundation Quality safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Moai Foundation Quality use?
Moai Foundation Quality is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Moai Foundation Quality use?
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.5k tokens, read only when the agent opens those files.
What are the alternatives to Moai Foundation Quality?
Skills that share tags, products or a category with Moai Foundation Quality: Test Guard (amElnagdy/guard-skills, 1.3k stars), Triage Sonarqube (netdata/netdata, 81k stars), Sonarqube Analysis (hbmartin/graphviz2drawio, 275 stars) and Code Solving (HoangTheQuyen/think-better, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Moai Foundation Quality?
modu-ai (a GitHub organization) maintains it in modu-ai/moai-adk, which has 1,230 GitHub stars. The repository holds 48 skills in this directory. The repository was last updated on October 9, 2026.
Source: modu-ai/moai-adk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.