quinotospec-refresh-discovery

quinotospec-refresh-discovery is a skill for Cursor from Quinoto-Tech/QuinotoSpec. It costs 31 tokens per session (735 once invoked), scanned A, original, MIT.

A workflow that updates only the project-discovery files affected by recent changes. It relies on an earlier full discovery and can target the whole project or one service.

In plain words
What is it for?
Use it to check the last discovery date, find changed files, and refresh the relevant discovery documents.
Why use it?
It avoids regenerating every discovery file when only part of a project has changed.

Skill for Cursor

Written for Cursor: shipped in a Cursor plugin.

Part of the quinotospec plugin — 90 skills, 9 agents, 1 hook shipped together

Good fit Use it to check the last discovery date, find changed files, and refresh the relevant discovery documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/quinoto-tech/quinotospec/quinotospec-refresh-discovery
Install

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.

Any agent
npx skills add Quinoto-Tech/QuinotoSpec --skill quinotospec-refresh-discovery
Clone the repo
git clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpec

Made for: Cursor.

Or install quinotospec, the plugin that ships this one along with the rest of its 90 skills, 9 agents, 1 hook.

Wrote 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.

agentmods badge for quinotospec-refresh-discovery

README.md
[![agentmods](https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-refresh-discovery/github.svg)](https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-refresh-discovery)
Your own site
<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-refresh-discovery"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-refresh-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.

agentmods 80×15 button for quinotospec-refresh-discovery

Your own site · 80×15
<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-refresh-discovery"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-refresh-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 735 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00735
Opus 5.5 $0.00012 $0.00294
Sonnet 5.5 $0.00006 $0.00147
Haiku 4.5 $0.00003 $0.00073

Measured 1mo ago against content hash 488a93667f07, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

quinotospec-refresh-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.

agent-dist/skills/quinotospec-refresh-discovery/SKILL.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow: Refresh Discovery

Este workflow detecta qué ha cambiado en el proyecto desde el último discovery y actualiza únicamente los archivos de .quinoto-spec/discovery/ afectados.

Parámetro Opcional:

  • SERVICE_PATH: Ruta relativa al sub-proyecto a refrescar (ej. ./services/auth-service). Si no se especifica, opera sobre el directorio raíz del proyecto. Este parámetro es utilizado por quinotospec.stack-discovery cuando detecta discoveries desactualizados en servicios individuales.

Precondición: El discovery completo (quinotospec.discovery) debe haberse ejecutado al menos una vez en el directorio objetivo. Si no existe {{SERVICE_PATH}}/.quinoto-spec/discovery/ (o .quinoto-spec/discovery/ en la raíz), redirigir al usuario a ejecutar quinotospec.discovery primero.


Paso 1 — Verificar fecha del último discovery

  1. Lee .quinoto-spec/discovery/01-stack-profile.md y extrae el campo **Discovery Date:**.
  2. Calcula cuántos días han pasado desde esa fecha.
  3. Reporta: "Último discovery: [fecha] ([N] días atrás)".

Paso 2 — Detectar archivos modificados desde el último discovery

Busca archivos modificados desde la **Discovery Date:** extraída:

git diff --name-only HEAD@{<discovery-date>} HEAD

Si git no está disponible, listar archivos con fecha de modificación posterior al discovery date.

Clasifica los cambios por área de impacto:

Archivo modificado Discovery afectado
package.json, requirements.txt, go.mod, etc. 01-stack-profile.md
Archivos de rutas/controllers/views 04-endpoints-and-openapi.md
Archivos de modelos/migrations/schemas 05-data-and-services.md
.github/workflows/, Dockerfile, .env.example 06-devops-ci-security.md
Cualquier archivo con bugs/refactors significativos 07-findings-and-recommendations.md

Paso 3 — Regenerar solo los archivos afectados

Para cada archivo de discovery identificado como impactado:

  1. Leer el archivo actual de discovery.
  2. Analizar los cambios en el código fuente relacionados.
  3. Actualizar solo las secciones afectadas del archivo discovery, manteniendo el resto intacto.
  4. Actualizar el campo **Discovery Date:** al día de hoy en 01-stack-profile.md.

Read the full file on GitHub · 70 lines

Changes

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.

  1. 1mo ago First seen · 70 lines · 31 tokens per session scan A 488a93667f07

Subscribe to this mod's changes

quinotospec-refresh-discovery is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 735 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.