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-initgit 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-init)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-init"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-init/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-init"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 294 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 298 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00060 | $0.05127 |
| Opus 5 | $0.00030 | $0.02563 |
| Sonnet 5 | $0.00012 | $0.01025 |
| Haiku 4.5 | $0.00006 | $0.00513 |
Grade A, and why
quinotospec-init 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 12d 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 — 579 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objetivo: crear la estructura base de .quinoto-spec/ en un proyecto nuevo, dejándolo listo para ejecutar @quinotospec.discovery como siguiente paso. No ejecuta discovery ni analiza el código — solo crea el esqueleto de directorios y archivos mínimos. Si el directorio está vacío (sin código ni archivos de configuración), el workflow ofrece generar un scaffold del proyecto.
Precondiciones
- El directorio de trabajo será la raíz del proyecto.
- Si
.quinoto-spec/ya existe, el workflow se detiene a menos que se use--force.
Paso 1 — Verificar estado actual
- Verificar si
.quinoto-spec/ya existe. - Si existe y NO se usó
--force:- Detener y mostrar: "
.quinoto-spec/ya existe. Usá--forcepara reinicializar (se preserva discovery y proposals existentes)."
- Detener y mostrar: "
- Si existe y se usó
--force:- Advertir que se sobrescribirán archivos de configuración (no discovery ni proposals).
- Pedir confirmación.
Paso 2 — Detectar si el proyecto está vacío
Revisar si el directorio contiene marcadores de un proyecto existente. Un proyecto se considera existente si contiene al menos uno de los siguientes:
package.json,Cargo.toml,pyproject.toml,go.mod,Gemfile,requirements.txt,Makefile,build.gradle,pom.xml,Dockerfile,docker-compose.yml,CMakeLists.txt,setup.py,setup.cfg,mix.exs- Directorios
src/,lib/,app/,include/ - Archivos de código fuente:
*.py,*.js,*.ts,*.go,*.rs,*.rb,*.java,*.kt,*.cs,*.c,*.cpp,*.h,*.ex,*.exs
Si el proyecto NO está vacío:
- Saltear los Pasos 3 y 4.
- Continuar directamente en el Paso 5 (Crear estructura de directorios).
Si el proyecto ESTÁ vacío y se usó --no-scaffold:
- Saltear los Pasos 3 y 4.
- Continuar directamente en el Paso 5.
Si el proyecto ESTÁ vacío y se usó --stack (ej. --stack python:fastapi:poetry:pytest:sqlite):
- Saltear el Paso 3 (wizard).
- Usar los valores del flag para el Paso 4 (scaffold).
- Validar que los valores sean válidos para el lenguaje elegido. Si algún valor no es válido, preguntar solo ese campo con el wizard.
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.
- 12d ago First seen · 579 lines · 60 tokens per session scan A 6be733873fcb
quinotospec-init is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 5,127 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…