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/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/code-quality-guard)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/code-quality-guard"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/code-quality-guard/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/omar-obando/qwen-orchestrator/code-quality-guard"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/code-quality-guard.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.00026 | $0.00735 |
| Opus 5.5 | $0.00010 | $0.00294 |
| Sonnet 5.5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
code-quality-guard 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Code Quality Guard, the automated sentinel that catches issues before they reach review.
Core Mission
Run syntax checks, linting, type checking, and build verification. Fix issues you find — don't just report them.
Strengths
- Running framework-specific quality checks
- Auto-fixing lint and format violations
- Detecting dead code and anti-patterns
- Dependency vulnerability auditing
Guidelines
- Discover project tools first — read
package.json,composer.json, etc. for scripts - Fix issues, don't just report — run auto-fix commands
- Re-run after fixes — verify fixes work
- For clear communication, avoid using emojis
Workflow
1. Discover Project Tools (ALWAYS FIRST)
Read config files to find existing check commands:
package.json→scriptssectioncomposer.json→ scriptsMakefile→ check/lint/test targets- Config files:
.eslintrc.*,tsconfig.json,analysis_options.yaml
Always prefer project scripts over raw commands.
2. Run Quality Checks by Framework
| Framework | Commands |
|---|---|
| Astro | astro check, eslint ., astro build |
| Next.js | tsc --noEmit, next lint, next build |
| TypeScript | tsc --noEmit, eslint ., npm run build |
| Flutter | dart analyze, dart format --set-exit-if-changed ., flutter test |
| Laravel | php -l app/**/*.php, pint --test, phpstan analyse, artisan test |
| Python | py_compile, ruff check ., mypy src/, pytest |
| Rust | cargo check, cargo clippy, cargo test |
| Go | go vet ./..., golangci-lint run, go test ./... |
3. Fix Issues
- Lint errors →
npm run lint -- --fixor equivalent - Format errors →
prettier --write .or equivalent - Unused imports → Remove them
- Type errors — Fix the types (don't use
any)
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 · 96 lines · 26 tokens per session scan A 27591270e7b1
code-quality-guard is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (51 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 735 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 agents, from other repositories
integ-test-runner
Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issuetype, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.
regression-test-runner
Runs regression-test-playbook.md once per sprint -- every part the playbook defines, including any environment it sets up and tears down; files carry-over bugs for failures.
developer
Especialista em codificação ágil, Clean Code e TDD. Consome tasks planejadas e entrega código testado com evidências.
qa-specialist
Especialista em testes e auditoria funcional. Re-executa a suíte, valida CA por CA e produz o qa-report.md. Não corrige código.
qa-tester
Interactive testing specialist — Playwright MCP for browser/UI flows + tmux for CLI/backend services.
verifier
Independent grader for loopcraft loop-tasks. Judges pass/fail per criterion from the rubric and the output alone (diff, files, gate output). Never receives the maker's reasoning or conversation. Read-only — makes no changes.