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-stack-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-stack-discovery)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-stack-discovery"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-stack-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-stack-discovery"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-stack-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.00027 | $0.01628 |
| Opus 5.5 | $0.00011 | $0.00651 |
| Sonnet 5.5 | $0.00005 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
quinotospec-stack-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 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Stack Discovery
Este workflow consolida los discoveries de múltiples sub-proyectos en un único .quinoto-spec/discovery/.
Precondición OBLIGATORIA: Dentro de todas las carpetas del root debe existir */.quinoto-spec/discovery/. De no ser así, detener el proceso y listar qué carpetas no tienen discovery para que el usuario ejecute quinotospec.discovery en cada una.
Paso 0 — Inventario de servicios
Antes de comenzar, escanea el root y lista todas las carpetas que contienen /.quinoto-spec/discovery. Para cada una, lee el campo **Discovery Date:** en su 01-stack-profile.md. Genera el inventario:
| Servicio | Ruta | Stack Principal | Discovery Date | Estado |
|---|---|---|---|---|
| [nombre] | [ruta relativa] | [lenguaje/framework] | [YYYY-MM-DD] | ✅ Fresco / ⚠️ Viejo |
Marcar como ⚠️ Viejo si el Discovery Date tiene más de 30 días de antigüedad (o si el campo no existe).
Si hay servicios con discovery ⚠️ Viejo:
- Notificar al usuario: "Los siguientes servicios tienen un discovery desactualizado: [lista]. Se recomienda ejecutar
@quinotospec.refresh-discoverypara cada uno antes de consolidar." - Esperar confirmación del usuario:
- Opción A — Refrescar primero (recomendado): Para cada servicio viejo, ejecutar el workflow
quinotospec.refresh-discoverypasando elSERVICE_PATHcorrespondiente. Continuar con la consolidación una vez que todos estén frescos. - Opción B — Consolidar de todas formas: Continuar con los datos actuales y documentar en
02-overview.mdqué servicios tienen discovery potencialmente desactualizado.
- Opción A — Refrescar primero (recomendado): Para cada servicio viejo, ejecutar el workflow
Este inventario queda documentado al inicio de los archivos consolidados y en el changelog.
Generación de archivos consolidados
Explora el proyecto completo y genera 8 archivos Markdown independientes en .quinoto-spec/discovery/ con los siguientes nombres EXACTOS:
- 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
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 · 118 lines · 27 tokens per session scan A ae5f221a5da6
quinotospec-stack-discovery is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,628 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-09-03.
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.