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 andregusman-raiz/a-gusman-claude --skill ag-meridiangit clone --depth 1 https://github.com/andregusman-raiz/a-gusman-claudeWrote 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/andregusman-raiz/a-gusman-claude/ag-meridian)<a href="https://agentmods.dev/skills/andregusman-raiz/a-gusman-claude/ag-meridian"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-meridian/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/andregusman-raiz/a-gusman-claude/ag-meridian"><img src="https://agentmods.dev/badge/skills/andregusman-raiz/a-gusman-claude/ag-meridian.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00055 | $0.00775 |
| Opus 5.5 | $0.00022 | $0.00310 |
| Sonnet 5.5 | $0.00011 | $0.00155 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
ag-meridian 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.
What it actually says
MERIDIAN — Maquina Autonoma de Qualidade de Software
Invocacao
/meridian https://app.example.com # App deployada
/meridian ~/Claude/GitHub/raiz-platform # Projeto local
/meridian https://app.example.com --threshold 90 # Threshold customizado
/meridian https://app.example.com --audit-only # So diagnosticar
/meridian --resume # Retomar run interrompido
/meridian ~/Claude/GitHub/fgts-platform --scope "/dashboard,/consultas" # Rotas especificas
O que faz
Executa QA completo AUTONOMO em 5 fases:
- SCOUT — Mapeia toda a aplicacao (rotas, features, auth, dados)
- SIEGE — Testa 5 dimensoes:
- D1-ALIVE: Carrega sem erros?
- D2-REAL: Dados sao reais (nao mock)?
- D3-WORKS: Features funcionam?
- D4-LOOKS: Visual correto em 4 viewports? (usa ag-capturar-tela para apps desktop/nativos)
- D5-FEELS: Cliente aceitaria? (narrativa)
- FORGE — Corrige bugs encontrados em sprints
- CONVERGE — Calcula MQS, loop ate >= threshold
- DELIVER — Quality Certificate, Fix PR, baselines, issues
Execucao
Spawnar o agent principal:
Agent({
subagent_type: "ag-meridian",
prompt: "{input do usuario}",
run_in_background: true,
mode: "auto"
})
Artefatos Produzidos
| Artefato | Arquivo |
|---|---|
| Quality Certificate | docs/meridian-certificate-YYYY-MM-DD.md |
| Fix PR | GitHub PR com before/after |
| Baselines | meridian-baselines.json |
| State (recovery) | meridian-state.json |
| KB Update | ~/.claude/shared/meridian-kb/ |
| Issues backlog | GitHub Issues com label meridian-finding |
Agents Delegados
| Agent | Fase | Proposito |
|---|---|---|
| ag-explorar-codigo | SCOUT | Explorar codebase |
| ag-testar-ux-qualidade | SIEGE D4 | Visual quality testing |
| ag-corrigir-bugs | FORGE | Bugfix em sprints |
| ag-corrigir-tipos | FORGE | Fix TypeScript errors |
| ag-depurar-erro | FORGE | Debug de bugs obscuros |
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 · 77 lines · 55 tokens per session scan A 59dee7923d72
ag-meridian is a skill published in the GitHub repository andregusman-raiz/a-gusman-claude (18 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 775 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-03.
Other skills, from other repositories
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
reality-verification
This skill should be used when the user asks to "verify a fix", "reproduce failure", "diagnose issue", "check BEFORE/AFTER state", "VF task", "reality check", "check test quality", "mock-only tests", or needs guidance on verifying fixes by reproducing failures before and after implementation, or detecting mock-heavy…
debugging
Playwright test debugging conventions for the scaffold — reading failure messages, classifying failure modes (TimeoutError, ZodError, strict-mode violation, locator not found, network errors, schema drift), the playwright.config.ts capture defaults (trace on-first-retry, screenshot only-on-failure, video…
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…