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-refresh-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-refresh-discovery)<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.
<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>- 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.00031 | $0.00735 |
| Opus 5 | $0.00015 | $0.00367 |
| Sonnet 5 | $0.00006 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
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 9d 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 — 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 porquinotospec.stack-discoverycuando 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
- Lee
.quinoto-spec/discovery/01-stack-profile.mdy extrae el campo**Discovery Date:**. - Calcula cuántos días han pasado desde esa fecha.
- 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:
- Leer el archivo actual de discovery.
- Analizar los cambios en el código fuente relacionados.
- Actualizar solo las secciones afectadas del archivo discovery, manteniendo el resto intacto.
- Actualizar el campo
**Discovery Date:**al día de hoy en01-stack-profile.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.
- 9d ago First seen · 70 lines · 31 tokens per session scan A 488a93667f07
quinotospec-refresh-discovery is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 735 once invoked, about $0.0002 per session on Opus 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.