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 IAPro-Community/Orquestrador-Maestro --skill skill-engineering-qualitygit clone --depth 1 https://github.com/IAPro-Community/Orquestrador-MaestroWrote 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/iapro-community/orquestrador-maestro/skill-engineering-quality)<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-engineering-quality"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-engineering-quality/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/iapro-community/orquestrador-maestro/skill-engineering-quality"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-engineering-quality.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.00046 | $0.00787 |
| Opus 5.5 | $0.00018 | $0.00315 |
| Sonnet 5.5 | $0.00009 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
skill-engineering-quality 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 17d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Quality
Apply a maintainable quality baseline to the repository that actually exists. Detect the stack first, preserve healthy conventions, and change only the gaps that matter.
Workflow
- Read repository instructions and manifests before editing:
AGENTS.md, package/build manifests, lockfiles, tool configs, CI files, and workspace definitions. - Build a stack map for every relevant module. Use manifest/build evidence before file-extension guesses. In monorepos, classify modules independently.
- Inventory existing format, lint/static analysis, type checking, tests, build, security checks, hooks, and CI.
- Compare the inventory with the applicable stack reference. Prefer existing healthy tooling; add or migrate tools only when there is a concrete gap or incompatibility.
- Implement the smallest coherent delta. Keep one owner per concern: formatter formats, linter/static analyzer finds semantic issues, compiler/type checker checks types, tests verify behavior, CI is the authoritative gate.
- Run project-native checks, fix real failures, and re-run from the final state. Keep autofix commands separate from check-only quality gates.
- Report detected stacks, changed baseline, commands executed, evidence, and remaining risks.
Load References Selectively
- Always read
references/discovery.md. - JavaScript/TypeScript, Node, React, Next, Vue, Nuxt, Angular, Svelte, SvelteKit, Astro, React Native: read
references/javascript-typescript.md. - Go: read
references/go.md. - Java/Kotlin or .NET: read
references/jvm-dotnet.md. - Python, PHP, Ruby, Rust, Elixir, Dart/Flutter: read
references/python-php-ruby-rust.md. - Hooks/CI/quality command design: read
references/quality-gates.md.
Guardrails
- Do not install ESLint merely because a frontend exists. If Biome or another healthy equivalent is already authoritative, preserve it.
- Do not introduce competing formatters, test runners, package managers, lockfiles, or build systems.
- Do not replace a working tool only because this skill prefers another.
- Do not silence failures with blanket disables,
any,@ts-ignore,nolint, skipped tests, or equivalent shortcuts. - Do not mass-upgrade dependencies as a side effect. Use
skill-dependency-upgradewhen an upgrade becomes a real workstream. - Do not redesign product UI here. Use
skill-frontend-excellencefor visual/product frontend work. - Do not turn a simple formatter/config edit into multiagent work.
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.
- 17d ago First seen · 59 lines · 46 tokens per session scan A a992a5ddcadd
skill-engineering-quality is a skill published in the GitHub repository IAPro-Community/Orquestrador-Maestro (58 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 787 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-09-30.
Other skills, from other repositories
beevibe-verify-pr
CI verification before marking a PR-bearing task done. Use BEFORE calling mcpbeevibeupdateprogress(done) on any session whose deliverable is a pull request — including the first dispatch (you opened the PR with gh pr create) and any revision dispatch (you pushed new commits to an existing PR). Watches the PR's…
cao-contributing
Contribute changes to the CAO (CLI Agent Orchestrator) codebase — the local dev loop, the CI gate map, and the pre-PR checklist. Use when the user says "open a PR", "why did CI fail", "run the checks before I push", "the mypy/Code Quality job is red", "add a test and verify coverage", or when making any code change…
staging-validation-phase
Guides manual staging validation before production deployment through smoke tests, critical user flow testing, data migration verification, and rollback capability checks. Use when validating staging deployments, running pre-production tests, or preparing for production promotion in staging-prod deployment model.…
evaluate
Use when the user wants a quality review, interaction audit, or to test the workflow against realistic scenarios.
matlab-testing-ci
MATLAB R2026a testing, validation, and CI workflow for matlab.unittest, MATLAB Test, Simulink Test, coverage, artifact generation, GitHub Actions, and open-source reproducibility. Use whenever MATLAB work needs verification, regression tests, CI, GitHub publication, or acceptance criteria.
systems-engineering
Systems engineering covering requirements management, the V-model lifecycle, integration planning, verification and validation (V&V), interface control, trade studies, and the NASA Systems Engineering Handbook. Spans the full lifecycle from concept through operations and disposal. Includes requirements decomposition…