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 Quinoto-Tech/QuinotoSpec --skill quinotospec-conflict-detectorgit clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpecWrote 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/quinoto-tech/quinotospec/quinotospec-conflict-detector)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-conflict-detector"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-conflict-detector/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/quinoto-tech/quinotospec/quinotospec-conflict-detector"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-conflict-detector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.01029 |
| Opus 5.5 | $0.00016 | $0.00412 |
| Sonnet 5.5 | $0.00008 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
quinotospec-conflict-detector 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 2mo 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Conflict Detector
Analiza una propuesta nueva o en curso y detecta conflictos potenciales con otras propuestas activas en .quinoto-spec/proposals/. Útil antes de crear una propuesta o durante la planificación de sprints.
Instrucciones de Ejecución
Paso 1 - Recibir input
Recibir uno de:
--proposal-slug {{SLUG}}: analiza una propuesta existente contra las demás--proposal-description "{{DESCRIPCION}}": analiza una propuesta futura contra las activas (modo pre-creación)--all: analiza todas las propuestas activas entre sí (modo auditoría global)
Paso 2 - Recolectar propuestas activas
- Listar todas las carpetas en
.quinoto-spec/proposals/(excluyendo_archived/) - Para cada propuesta activa, leer
proposal.mdy extraer:- Servicios Afectados (metadatos iniciales)
- Archivos nuevos/modificados (sección "Impacto en el Sistema")
- Dominios/flujos (sección "Arquitectura y Diseño Técnico")
- Prioridad y Estado
Paso 3 - Detectar conflictos
Comparar la propuesta objetivo contra cada propuesta activa (o todas contra todas en modo --all):
| Nivel | Condición | Severidad |
|---|---|---|
| CRÍTICO | Mismos archivos Y mismo servicio | 🔴 Bloqueante |
| ALTO | Mismo servicio, archivos distintos | 🟠 Revisar orden |
| MEDIO | Mismos flujos/dominios, servicios distintos | 🟡 Coordinar |
| BAJO | Mismo tipo de cambio (ej. dos refactors) | 🟢 Informativo |
Paso 4 - Generar reporte
Formato del reporte:
Conflict Detector — {{PROPOSAL_SLUG o "Análisis Global"}}
────────────────────────────────────────────────────────
🔴 CRÍTICOS ({{N}})
| Propuesta A | Propuesta B | Conflicto |
| auth-jwt | auth-refresh | Archivo: auth-service/token.go |
🟠 ALTOS ({{N}})
| Propuesta A | Propuesta B | Conflicto |
| pay-v2 | pay-refund | Servicio: payment-service |
🟡 MEDIOS ({{N}})
| Propuesta A | Propuesta B | Conflicto |
| notif-email | notif-push | Dominio: notificaciones |
🟢 BAJOS ({{N}})
| Propuesta A | Propuesta B | Observación |
| refactor-db | refactor-api | Ambos son refactors |
────────────────────────────────────────────────────────
Total: {{N}} conflictos | {{CRITICAL_COUNT}} críticos
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.
- 2mo ago First seen · 104 lines · 40 tokens per session scan A fffc0d55582d
quinotospec-conflict-detector is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,029 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 skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.