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-discoverygit 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-discovery)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-discovery"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-discovery/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-discovery"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-discovery.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.00021 | $0.01346 |
| Opus 5.5 | $0.00008 | $0.00538 |
| Sonnet 5.5 | $0.00004 | $0.00269 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
quinotospec-discovery 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Discovery
Explora el proyecto completo y genera 8 archivos Markdown independientes dentro de .quinoto-spec/discovery con los siguientes nombres EXACTOS (dentro del proyecto):
- 01-stack-profile.md
- 02-overview.md
- 03-architecture.md
- 04-endpoints-and-openapi.md
- 05-data-and-services.md
- 06-devops-ci-security.md
- 07-findings-and-recommendations.md
- 08-product-and-agreements.md
Instrucciones generales (aplican a todos los archivos):
- Escribir en español, formato claro y profesional.
- Cada archivo debe comenzar con un título H1, una breve descripción y una "ruta de guardado" al inicio, por ejemplo: "Guardar en: .quinoto-spec/discovery/02-overview.md".
- Usar subsecciones (H2/H3) para organizar hallazgos: Resumen, Detalle, Pasos para reproducir/ejecutar, Recomendaciones.
- Incluir listings de archivos/carpetas relevantes con rutas relativas, comandos para ejecutar la aplicación (dev/build/test), y ejemplos de salida cuando aplique.
- Generar siempre diagramas de secuencia en Mermaid (
sequenceDiagram) para los flujos principales del sistema (ej. request/response de endpoints, flujos de autenticación, integraciones externas). Para diagramas de arquitectura o ER que no se puedan inferir con certeza, usar un placeholder indicando qué debe contener. - Generar contenido accionable y conciso: checklists, comandos sugeridos, y prioridades (alta/media/baja).
- Detecta y documenta frameworks, librerías y versiones (package.json, requirements, etc.).
- Detecta y documenta pruebas automatizadas: tipos detectados (unit, integration, e2e), cómo ejecutarlas, cobertura actual si es medible (ej.
--coverage), y qué áreas críticas no tienen tests. Contenido por archivo:
- 01-stack-profile.md
- Skill Requerida: Ejecuta primero la skill
quinotospec-stack-detect. - Identificación precisa del stack tecnológico (Lenguaje, Frameworks, Package Manager, Test Runner).
- Detalla los Coding Standards detectados (ej. Service Layer, Hooks, etc.).
- 02-overview.md
- Resumen ejecutivo del proyecto (qué hace, contexto, lenguaje/plataforma).
- Información del repositorio: estructura de carpetas principales y archivos de entrada.
- Comandos básicos (dev, build, test) y pre-requisitos de entorno.
- Lista rápida de riesgos y puntos críticos identificados.
- 03-architecture.md
- Diagrama conceptual (Mermaid placeholder) y descripción de la arquitectura (capas, módulos, responsabilidades).
- Patrón(es) de diseño observados.
- Diagrama de secuencia real en Mermaid (
sequenceDiagram) mostrando el flujo de datos entre los componentes principales: cliente → controlador/router → servicio → repositorio/DB. Si hay integraciones externas, incluirlas. - Componentes reutilizables e integraciones internas.
- 04-endpoints-and-openapi.md
- Mapeo de endpoints REST y GraphQL detectados (ruta, método, parámetros, respuesta esperada).
- Generar un OpenAPI/Swagger mínimo (YAML o JSON) con los endpoints principales detectados y ejemplos de request/response.
- Notas sobre autenticación/autorización en endpoints.
- Recomendaciones para pruebas de integración de API.
- 05-data-and-services.md
- Documentación de bases de datos y esquemas (tablas/colecciones principales, campos importantes).
- Servicios externos integrados y sus propósitos (APIs, proveedores, SDKs).
- Estructura de estado global (si aplica) y modelos de datos.
- Scripts de migración, seeds, y acceso a datos (cómo correrlos).
- 06-devops-ci-security.md
- Configuración de entorno de desarrollo y variables sensibles requeridas.
- Pipelines de CI/CD detectados (GitHub Actions, GitLab CI, etc.) y pasos de despliegue.
- Scripts de automatización y cron jobs detectados.
- Revisión rápida de prácticas de seguridad (gestión de secretos, políticas CORS, validaciones).
- Auditoría de dependencias: ejecutar o documentar el comando de auditoría correspondiente al stack (
npm audit,pip-audit,bundle audit, etc.) y listar las vulnerabilidades críticas o altas encontradas con su CVE si está disponible. - Estrategias de backup, versionado y recuperación respecto a datos y despliegues.
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 · 86 lines · 21 tokens per session scan A 6de82cdc0820
quinotospec-discovery is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 1,346 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 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.